I currently have all my teams setup w/ the correct sprint point velocity, and a release scheduled for a fixed time period. However, the timeline is showing up as RED and the release is showing as "overbooked". How can this be when I have more than enough resources to cover 5x the # of points?
Also, changing the velocity of the team does nothing to impact this. Is this a bug?
Aaron, my guess is that this has to do with the "Maximum assignees per story" configuration option of the plan. If you have people assigned to your teams and the value of that field is less than number of people on each team, Portfolio will limit the amount of work that can be done concurrently. I questioned this in another thread here somewhere.
I am facing the same issue.
I have one release which has 3 issues to be addressed.
The team has 120 hrs to do.
Cumulative estimation of the estimated work is 16 hrs.
But portfolio is showing estimated release date after 2 months.
Is here any issue with my configuration?
I only seem to be able to 'solve' this when I change the enddate of release X to be a day before the start of release Y. Which is weird as that means I have to end the release on a Sunday...???
So it seems portfolio doesn't take into account that Saturday and Sunday are marked as non-working days.
There is an issue reported that seems similar to this: https://jira.atlassian.com/browse/JPOSERVER-1756
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot