we have the following situation when using Portfolio 2:
Now when trying to use Portfolio 2.0 the plan properly imports the sprints from the single board (which is used as source) but it is not able to resolve the fact that the sprins are happening concurrently. Note that it seems not to be possible to define the dates for the future sprints (which weren't started yet). As result automated scheduling is not usable.
Is it possible to configure e.g. mapping of the sprints and the agile teams or any other way to tell Portfolio plan to align the sprints properly?
Thanks in advance
That unfortunately does not work - the boards show automatically the sprints that the issues inside are put on. In theory this probably is the solution but means I need to separate the backlog for each scrum (so that the board does not show issues from the same JIRA project but somehow labeled as belonging to other SCRUM. And this is sth I would like to avoid - in general 3 scrums are planning their work separately but it does happen that we switch some of the stories to other scrum - depending on the progress and priority of the issues (if one scrum is faster and others have delay then they take over high priority issues before working on their original lower priority items). The the trick is to share the backlog but somehow properly sequence the sprints...
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
We recently launched a brand new Portfolio for Jira demo where you can learn: The essentials for getting started with Portfolio for Jira How to create a realistic roadmap based on your work in Jir...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs