We are currently switching to the new live portfolio plan, and are quiet pleased with it over all.
However, we're having an issue with the automatic story scheduling. The issue we're having is that stories that are currently planned in our active sprint and badly incorporated in the project scope and timeline. Instead of appearing at the very stop of the story list in the scope view, they seem to be placed randomly. This completely messes up our estimate release dates, as the plan places tasks that will be completed this week to many weeks ahead.
Is this a known issue, or are we missing something?
Hi @Alex Pabouctsidis, is the active sprint correctly picked up by Portfolio at all, i.e., do you see its sprint name in the schedule if you look at the stories view?
The active sprint is considered only if the plan is connected to a board, and if that board is linked to the team as the "preferred issue source" (little dropdown directly under the team name in team management) - in this case, you should see active sprints showing up for that team, and then also assignments into that sprint should be respected and overrule priority order or other constraints.
If that doesn't answer the problem, I'd suggest to raise a support ticket to investigate further. Thanks!
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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