-
Suggestion
-
Resolution: Timed out
-
0
-
2
-
NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding suggestion.
The blurb for JIRA Portfolio describes how the tool can be used to sketch out multiple, alternative-future plans and then activate the chosen one (by synchronising with JIRA I guess). I take this to mean that you can have a master plan currently running, fork it off to draft a possible alternate plan, then declare that alternate plan to be the master plan once you're happy with it.
However, because the Plan owns the Team definitions, if any team settings change on the current master plan (e.g. new members, leave dates) while a new plan is in draft, you have to manually bring those changes across. When trying to plan for 200+ people, this is near impossible.
To plan large work programs in practice, I need to be able to migrate team, skills and stages data between plans. Much better though would be for that data to be factored-out of my plan, so that I can have two or more plans live-linking to a common set of Team records. I.e. give me the option of having plans that just use Teams, rather than own them.
- is related to
-
- Gathering Interest
- relates to
-
- Closed
[JRACLOUD-89563] Import/Export just for Teams
Deleted Account (Inactive)
added a comment - Duncan,may I add the following: When we "design" the next level of our program portfolio, we usually consider multiple ressource constellations to estimate time and costs. So we're thinking in m backlog variants and n ressource variants. Playing in the same league 200+
Deleted Account (Inactive)
added a comment - Duncan,may I add the following: When we "design" the next level of our program portfolio, we usually consider multiple ressource constellations to estimate time and costs. So we're thinking in m backlog variants and n ressource variants. Playing in the same league 200+ 
Duncan Fletcher
added a comment - Note, this idea is a little more than what JPO-141 is proposing. I'm further suggesting an ability to draft some team changes in one plan, then see what those same changes look like in another plan, etc. I.e. more dynamic than just "shared teams".
Duncan Fletcher
added a comment - Note, this idea is a little more than what JPO-141 is proposing. I'm further suggesting an ability to draft some team changes in one plan, then see what those same changes look like in another plan, etc. I.e. more dynamic than just "shared teams". 
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team - Jira Cloud Product Management