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?
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
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?
This approach requires you to have the JIRA administrative rights. The main aim of this article is to help you achieve an organized, easy-to-maintain workflows in your JIRA instance thereby, reducin...
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