Portfolio live plan shows as overbooked when it should NOT be

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?

5 answers

This widget could not be displayed.

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

This widget could not be displayed.

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.

This widget could not be displayed.

@Peter Callies - unfortunately thats not it. I've changed that setting (and all other settings for that matter) and the dates NEVER change after recalculation. Leads me to believe they just don't work....

This widget could not be displayed.

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 widget could not be displayed.

For me the solution was the "" - in the configuration. It was set to on which caused the separate stages of a work item to be scheduled sequentially into separate sprints. With the setting changed to 'off' it works as expected for me now.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted yesterday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

79 views 1 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you