youngmon/atlassian-qna huggingface dataset:
Single sprint for multiple projects
Asked by Robb Duke:

Hello community.

I have a software project using scrum and we operate in sprints. This is a team managed project.

I also have multiple business projects that are team managed.

What I would like is to have all projects operate under a single sprint, so we are all on the same page.

We can accomplish it be "knowing" but I would like the sprint feature to carry over unfinished issues from sprint to sprint.

First question: is this possible?

Second question: Do all the current projects need to be re-created as company-managed projects (since I understand you cannot convert a team to company-managed)

Thank you!


Answers:
author: Tansu Akdeniz
body: Hi [@Robb Duke](/t5/user/viewprofilepage/user-id/4921073)

As I know, company-managed project is needed. Since there is no automatic conversion, you need to manually handle this process by creating a new company-managed project. Then, you can simply create a Scrum board and provide a filter which includes all related projects. So, you can operate all tasks from different sprints under single sprint and board.

comments: author: Robb Duke
body: Thank you [@Tansu Akdeniz](/t5/user/viewprofilepage/user-id/472390)

When I create the filter as you suggest, will only company-based projects be available? Or can it use the team-based projects I already have created?

If not, is it possible to move issues from a team-based project to a company-based project?


author: Mika Nagaya
body: Hi [@Robb Duke](/t5/user/viewprofilepage/user-id/4921073) ,

Thank you so much for your participation in the Atlassian community!

It sounds like your organisation is using both Jira Software and Jira Work Management. We are doing further research on **customers who use both Jira Work Management and Jira Software**, and we would love to invite you to take part in an upcoming customer research study!

**What's involved in the research:**

* Sessions are 1 hour and conducted over video-conference, so you can participate from anywhere around the globe.
* During the research, we'll start with a general chat to get to know you, then ask some questions about your experience using both Jira Work Management and Jira Software.
* As a token of our appreciation, you'll receive an e-gift card worth $100 USD within 5 days of completing your session.

If you're interested and would like to participate, please take this short survey <https://www.userinterviews.com/projects/_EGjxvzWRA/apply>. *(Alternatively, you can refer anyone who you think might be interested in the study!)*

If you're eligible for the study, we will reach out to schedule a time that is suitable for you.

If you have any other questions at all, feel free to email me at [mnagaya@atlassian.com](mailto:mnagaya@atlassian.com). We look forward to meeting you!

Cheers,

Mika

Agile and DevOps Research

comments: author: Andy Rosengard
body: How did this activity go? My company is using both features.


Tags: cloud
Is the JIRA portfolio "improved planning design" available in JIRA Cloud - or else, when will it be?
Asked by Jordi Camps:

I'm starting with JIRA portfolio and seeing a lot of references in the documentation to the "improved planning design", which seems much more convenient.

All my research seems to point that this is only available as a download for JIRA server and such - is that right? I'm surprised the last Portfolio version on JIRA Cloud seems to be over a year old and I can see no plans regarding that upgrade - when can we expect, as paying customers to both JIRA and Portfolio, to have the new experience available?

Thx,


Answers:
author: Earl McCutcheon
body: Hi Jodi,

There are some changes on the horizon coming soon but we do not have much of plan details yet for the the overall design but the current details that we do have avaliable so far were brought up in following Portfolio Article Post on community back in May that covers the future plans for the improved interface in cloud:

* <https://community.atlassian.com/t5/Portfolio-for-Jira-articles/Top-20-questions-and-answers-about-Portfolio-3-0/ba-p/1085208>

Noting:
>
> ### Portfolio for Jira Cloud {#toc-hId-1087098431}
>
> #### Will the capabilities of Portfolio for Jira Server and Data Center 3.0 be available in Cloud? {#toc-hId-1777659905}
>
> Portfolio for Jira Cloud continues to be an important planning solution for Jira Software Cloud customers using the Classic project template. Portfolio for Jira Cloud won't be going anywhere any time soon, although no major product enhancements are planned at this time.
>
> At US Summit 2019, we announced a new planning solution for customers on Jira Software Cloud's next-gen templates (aka 'the new Jira'). These new planning features are all natively built into Jira Software Cloud and include: roadmaps with hierarchy, the ability to forecast timelines for epics, dependency mapping, and capacity management functionality. All of these new features will be bundled into our new Jira Software Premium offering.
>
> We recommend Portfolio for Jira Cloud for customers on our Classic templates and Jira Premium for customers on next-gen templates.
>
> Jira Premium is currently available for early access. Customers can sign up or learn more at[atlassian.com/premium](http://atlassian.com/premium).

Regards,  
Earl

comments: author: Earl McCutcheon
body: Hello again,

Also there are some more details on this for Portfolio for Jira Cloud in the comment from Jake Brereton on [this article](https://community.atlassian.com/t5/Portfolio-for-Jira-articles/Introducing-a-new-planning-experience-in-Portfolio-for-Jira/ba-p/944996/page/3#M98) where he answered another community member that had the same question as you.

Regards,  
Earl


Tags: advanced-roadmaps
How do I assign issues to a cross project release?
Asked by Annette Banes:

I have a portfolio plan with 3 project and several cross project releases that apply to all 3 projects. How do I assign the issues in the 3 projects to the cross project releases?


Answers:
author: Earl McCutcheon
body: Hi Annette,

Once you have created a cross project release in the Plan and associated the projects to the release as covered in ["Creating and configuring cross-project releases"](https://confluence.atlassian.com/jiraportfoliocloud/creating-and-configuring-cross-project-releases-828785313.html) adding the issues to the release can be done either by setting the release in the "Releases: column:

![Screen Shot 2019-08-21 at 4.23.39 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/63982i448B7D5A463F07DC/image-dimensions/155x102?v=v2 "Screen Shot 2019-08-21 at 4.23.39 PM.png")

OR you can set the version in the issue directly via the Fix Version Field, below is a screenshot for the same issue in both the New issue view and The Classic view to highlight the difference in location:

![Screen Shot 2019-08-21 at 4.28.30 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/63983iB39477A9A90C8FF3/image-dimensions/184x124?v=v2 "Screen Shot 2019-08-21 at 4.28.30 PM.png") \& ![Screen Shot 2019-08-21 at 4.25.20 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/63984iEC08D301609576D5/image-dimensions/318x118?v=v2 "Screen Shot 2019-08-21 at 4.25.20 PM.png")

Regards,  
Earl


Tags: advanced-roadmaps
Does Jira Portfolio 3.7.0 support scheduling unestimated items based on default estimates?
Asked by Lindsay Czopur:

I only see the feature to schedule unestimated items based on default estimats available in the Cloud version:

<https://confluence.atlassian.com/jiraportfoliocloud/scheduling-unestimated-items-based-on-default-estimates-844236853.html>

Is this something that is available in the server version? We are currently trialing v3.7.0. Thanks!


Answers:
author: Earl McCutcheon
body: HI Lindsay,

Scheduling unestimated issues is covered at the following link for Jira Server 3.7 but note that there are some differences between the Live plan view, which is currently what is avaliable in Jira cloud, and this does not apply to the new planning experience, where Live plans and the new experience are both avaliable in Server:

* [Scheduling unestimated items](https://confluence.atlassian.com/jiraportfolioserver037/scheduling-unestimated-items-975036058.html)

If your using the New Planning Experience view for your plan, the scheduling is going to base the target dates on the estimates, and additional details can be seen at:

* [Scheduling work](https://confluence.atlassian.com/jiraportfolioserver037/scheduling-work-975035927.html)
* With some specifics on the differences in the child page: ["Auto-scheduling issues"](https://confluence.atlassian.com/jiraportfolioserver037/auto-scheduling-issues-975035937.html)

> Scheduling unestimated issues:
>
> * Live plans:
>   * If an unestimated issue is assigned to a release, the scheduler will use the dates of this release to schedule the issue by default.
>
>     You can configure[how to schedule unestimated issues](https://confluence.atlassian.com/jiraportfolioserver037/scheduling-unestimated-items-975036058.html)in a live plan.
> * Plans with the improved interface
>   * By default, the scheduler uses target dates to schedule unestimated issues, and the issues will be scheduled to last the duration of their target dates.
>
>     For unestimated issues that are assigned to any*sprint* ,*release* , or*team* ,***the values for these will persist*** regardless of the[auto-scheduled settings](https://confluence.atlassian.com/jiraportfolioserver037/auto-scheduling-issues-975035937.html#Auto-schedulingissues-autoschedulesettings)that you've configured.

Regards,  
Earl


Tags: advanced-roadmaps
Export dependencies to excel?
Asked by AVA St-Pierre:

HI,

Anyone is able to export dependencies report from Jira?

Thank you!!


Answers:
author: Mike Anderson
body: If you set a filter for your issues, then choose to Export (all fields), there will be a field called "Outward issue link (Gantt End to Start)". This is a "successor" field, showing which issues by ID are dependent upon this issue to be completed before they can start.

If you only use start-to-finish types of dependencies then you can import this into MS Project. (probably a different thread)


author: Avri Glick
body: Hello,  
Is there any plan/ due date for this implementation?  

Regards,  
Avri


author: Petter Gon?alves
body: Hello AVA,

As [@Ang?lica Luz](/t5/user/viewprofilepage/user-id/986290) mentioned, The Dependencies Report of JIRA Portfolio cannot be exported, as described in this [documentation](https://confluence.atlassian.com/jiraportfoliocloud/dependencies-report-937164926.html):
> * This report can be embedded in Confluence**but not exported.**

As a workaround, you can optionally embed it to a Confluence page and make it public to the persons you want, in case you want to do any presentation slides or something like this.

Let me know if you have any questions about it.


author: Ang?lica Luz
body: Hello there,

Welcome to Atlassian Community!  
Currently, it's not possible to export dependencies. We have a feature request suggesting the implementation of this ability:  
- <https://jira.atlassian.com/browse/JPOCLOUD-2072>  
Please, click on vote and watch in order to hear about updates on the development cycle.

Regards,  
Ang?lica


Tags: advanced-roadmaps

export

ms-excel
Portfolio 3.0 - auto schedule vs assignee
Asked by Ron Grosberg:

Hi,

When I do automatic planning - how is the assignee taken into consideration? will it always keep the same assignee but make sure that they are not over-allocated? is there any place that explains well how it is done?

By the way - I see that issues are always assigned to the size of a sprint, so that even if I think an issue takes 2d if my sprint is 2w, it will be allocated for the entire 2w, is this something that's going to stay?


Answers:
author: Ruslan Prakapchuk
body: Hi [@Ron Grosberg](/t5/user/viewprofilepage/user-id/3519949)

Yes, the assignee is taken in consideration and is not re-assigned by the scheduler. Scheduler algorithm does its best to not overbook a person when assigning previously unassigned issues to them. However, Portfolio 3.0 doesn't support individual capacity yet and each assignee gets an equal share of team capacity.

\> I see that issues are always assigned to the size of a sprint

In a Scrum sprint, issues are delivered at the end of the sprint, hence they are shown as size of the sprint by the scheduler. We do not have any plans to change this at the moment. You can manually adjust issue size in the roadmap if you wish.

More information about scheduler behaviour could be found at <https://confluence.atlassian.com/jiraportfolioserver/auto-scheduling-issues-967895245.html>

----

Portfolio for Jira Server Team

comments: author: Ron Grosberg
body: Thanks! that's good to know. I have a lot of experience from my previous job in trying to manage a roadmap for a group (I had \~35 people) I really hope that with the new portfolio we will be able to use everything inside jira as using multiple tools is really a pain in the neck...

Is there a roadmap I can see of what's coming when?


Tags: advanced-roadmaps
How to link an issue to an epic in the "Scope view"
Asked by Mirco:

Hey there,

is there no way to directly link epics to initiatives and stories/tasks/whatever to epics directly in the Scope view?

Because it's possible to create new tickets and it would be nice to not have to open the issue in a new tab to enter than the new epic.


Answers:
author: Earl McCutcheon
body: Hello Mirco,

To add a story to an Epic or adding an Epic to an Initiative from the scope view, select the issue that you want to link to the next hierarchy level up, to expand the details view for that issue and link it by setting the parent issue field with the desired parent issue:

![Screen Shot 2019-08-19 at 10.29.56 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/63658iEE3CD1B9A5AD0390/image-dimensions/214x117?v=v2 "Screen Shot 2019-08-19 at 10.29.56 AM.png")

Alternatively contingent on the current hierarchy level that you are looking at, you can expose the parent issue type as a column per the current Hierarchy level, i.e. when viewing the story level can expose the Epic column and viewing Epic you can expose the Initiative level, then you can set the parent link using the parent issue type column for the current level you're viewing:

![Screen Shot 2019-08-19 at 10.34.13 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/63659i4660C0F8B5849B58/image-dimensions/199x114?v=v2 "Screen Shot 2019-08-19 at 10.34.13 AM.png")

Regards,  
Earl


Tags: advanced-roadmaps
How can I remove or re-send a team invite in Jira Cloud?
Asked by Dan Hawkins:

I have sent an invite to one of my teams in Jira Coud. The user can not finf the invite I sent. So, I would like to re-send the invite. I am not able to see how I can do that. Thank you for your help!


Answers:
author: Petter Gon?alves
body: Hello Dan,

Welcome to Atlassian Community!

You can follow the steps below to properly remove your user and invite him again:

- Navigate to User management \> Find the user \> Click in **Show Details**:

![Screen Shot 2019-08-16 at 18.46.53.png](https://community.atlassian.com/t5/image/serverpage/image-id/63559i8EC6AA835369E644/image-dimensions/500x254?v=v2 "Screen Shot 2019-08-16 at 18.46.53.png")

- Click at the three dots menu in the top-right of the page \> **Remove**:

![Screen Shot 2019-08-16 at 18.47.08.png](https://community.atlassian.com/t5/image/serverpage/image-id/63560i3162EDF3B0078484/image-dimensions/493x114?v=v2 "Screen Shot 2019-08-16 at 18.47.08.png")

- Navigate back to the User management screen and invite the user again

Let me know if this information helps.


Tags: advanced-roadmaps

cloud

jira-cloud

team
Members Are Greyed Out In Jira Portfolio
Asked by Mark Griffiths:

I have created a team and given each member 37.5 hours. When I assign an epic to them for a sprint they're greyed out and the task doesn't show in the portfolio schedule. I have tried to recalculate the plan but it doesn't do anything. Some members are completely greyed out and so they have nothing assigned to them.

Why are the members greyed out even though they're not over allocated? How could I fix it?


Answers:
author: Rohan
body: Hi Mark,

You should make sure that you have Story Points set for the epic that you are assigning the team to.  
<https://confluence.atlassian.com/jiraportfoliocloud/configuring-the-availability-of-team-members-828785286.html>  

If you're using Skills and Stages you will also need to make sure that the team members assigned to the epic have the relevant skillsets.  
<https://confluence.atlassian.com/jiraportfolioserver/configuring-stages-and-skills-935577853.html>

If you're still having trouble after double checking this, any further context that you can provide about your specific setup (especially around team/skills configuration) would be helpful. Screenshots are also helpful if you're able to share.  

Best Regards,  
The Portfolio for Jira Server team.

comments: author: Mark Griffiths
body: It has worked before without me setting any story points, however I just added some story points to 1 epic and I didn't see it in the schedule. It stopped working when I got back from summer holiday, but I don't know what happened in between to say what caused it.

I set-up the teams correctly as the instructions in the link. I gave a start date but no end date and everyone has some hours allocated. I am not using skills or stages. The team is shared but some of the epics are shown in the schedule and others are not. The ones that are shown have the team members not in grey.

Maybe the root cause is why are the team members grey. Like said, they all have start dates, no end dates and hours allocated.


Tags: advanced-roadmaps
Portfolio: Grouping by project in view settings with active filter does not work
Asked by bugf1x:

Hi there,

not sure if this came with the last update, the problem is:

* I choose more than one project in filters
* I select group by 'project' in view settings
* the result is empty
* group by none or assignee works as intended

this definitely worked before. The same method works for other combinations. When I choose more than one assignee and group by assignee, the result shows me all issues for the assignees and groups by their name.


Answers:
author: Chiragkumar Rupani
body: Hi,

Thanks for sharing your feedback. This is definitely a buggy behavior. I have raised a JAC issue to work on it. You can track the progress by following the JAC issue.

<https://jira.atlassian.com/browse/JPOSERVER-2646>

If you have any other questions, please feel free to let us know.

Regards,

Portfolio for Jira


Tags: advanced-roadmaps
Can velocity be specified for individual team members in Jira Portfolio (Cloud)?
Asked by Amy Wilkinson:

We are currently experimenting with teams. Each team has a velocity assigned ("Forecast velocity" is selected for each team.) We would like to test different scenarios where we add new team members and see what it does to the plan. Unfortunately, it does not change the Forecast velocity at all and therefore does not change the plan. The only way I can get it to affect the plan is if I change the plan configuration to use hours instead of story points. Also, if I add a new person to the team, I can specify the weekly hours available for that team member, but not story points. I found some documentation about how to do it (link following below), but I don't see where this is. Maybe the documentation is for Jira Server and Cloud does not have this capability? Per the documentation:

"You can adjust upcoming velocity based on the availability of team members. When this option is selected, Portfolio for Jira will calculate the impact on the team velocity for any limited presence, absences, or weekly hours set in the [team member's detailed dialog](https://confluence.atlassian.com/jiraportfolioserver0216/managing-your-team-s-availability-957483801.html). The adjusted forecasted velocity for future sprints is displayed in the bar graph.

Portfolio for Jira makes the assumption that every resource (team member) contributes equally to the total team velocity."

Please advise! Thank you!

<https://confluence.atlassian.com/jiraportfolioserver0216/settings-estimates-with-story-points-957483445.html>


Answers:
author: Chris Melville
body: I would be happy if you could adjust forecasted story point velocity for the team as a whole. The only way to do this today is, as you suggest, using hourly forecasting.


Tags: advanced-roadmaps
Is there anything to look at for Portfolio when you migrate from Jira Cloud to another Jira Cloud%
Asked by Nicolas Perron:

On the project, we have Portfolio, Jira Cloud and Confluence Cloud. Soon, we will need to migrate all the data on a new Jira Cloud owning by our client. Is there anything in particuliar to look for when migrating the Portfolio app?


Answers:
author: Earl McCutcheon
body: Hi Nicolas,

Migrating cloud to cloud, the portfolio data should come through without issue, you will want to follow the ["Migrating from one Cloud instance to another Cloud instance"](https://confluence.atlassian.com/confeval/other-atlassian-evaluator-resources/migrating-from-one-cloud-instance-to-another-cloud-instance) guide using a Site backup method, and importing to the new cloud site with the portfolio application in place, and you should be good to go once migrated over.

However there is a issue with migrating next-gen project types currently, and as Portfolio is not compatible with Next-Gen project types you should not have any next-gen projects tied to the Portfolio plans unless you are ok with the limitations covered in ["Portfolio for Jira next-gen support"](https://confluence.atlassian.com/jiraportfoliocloud/portfolio-for-jira-next-gen-support-968663298.html) so the only limitation to look out for currently is if there is any next-gen project data coming over in the migration, covered in the XML migration document ["Exporting issues"](https://confluence.atlassian.com/adminjiracloud/exporting-issues-776636787.html) :
> Currently, exports that include next-gen software projects won't include any epic link or other relationship data between epics and their children issues. This is a known error and we're working to fix it. Thanks for your patience.

Regards,  
Earl


Tags: advanced-roadmaps
What is the current enterprise release of Portfolio for Jira (if any)?
Asked by Gregory VAN HOOF:

Hi,

We are considering to upgrade from Portfolio 2.13.1 to Portfolio 3.x.

We would like to know if Portfolio 3.x qualifies as Enterprise Release?

In addition, are there any precaution to take into account before doing the upgrade?

For example, can we guarantee users that existing live plans will be migrated without loosing any data?

Thank you,

Greg


Answers:
author: Roi Fine
body: Hi Gregory,

Glad to hear you are getting ready to get on the new Portfolio.

There is no enterprise release for Portfolio, enterprise releases are only available for Jira and Confluence.

There are no major precaution when updating from 2.13.1 to 3.x other than the fact that with the releases of Portfolio for Jira 3.0 and later, Portfolio will no longer support the use of classic plans (interface introduced in 1.x).

Important to note, that even when you upgrade, existing plans would still have the old UI, and users would have the option to opt in and out to the new interface.

Please find more info in our migration guide: <https://confluence.atlassian.com/jiraportfolioserver/migration-guide-859479290.html>

I hope that helps,

Roi Fine \| Product Manager

comments: author: Gregory VAN HOOF
body: Hi Roi,

Thank you very much for the clarification.

Gregory


Tags: advanced-roadmaps