Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to resolve under-utilized / empty sprints in portfolio automatic planning

Hi,

I have built my company roadmap into portfolio.

It is quite complex with several initiatives and epics. I have manually allocated teams to the various epics (for simplicity we defined only one stage - implementation, and one skill - development).

I have also defined a few versions with dynamic end dates, allocating each epic to a version.

Some dependencies are defined but a lot of the epics are not dependent on anything.

The problem I see is that at least one of the teams has gaps / empty sprints in the middle of their workplan, while the epics that populate the plan after the gaps could have started earlier (no dependencies). These epics belong to release 3 (meaning there are two releases beforehand) but I do expect the team to start working on them as soon as they are available, even if other teams are still working on release 1 or 2.

Even if I set the release 3 (and release 2) start date manually to today, this problem persists.

How can I resolve this?

Thanks

Ran

3 answers

1 accepted

0 votes
Answer accepted

Hi Ran, I've investigated this, and based on your description it is certainly expected that the epic in release 3 is scheduled as soon as a team is free to do it, given the release date is set as a fixed date allowing for an overlap between the releases. 

It seems this was a scheduling bug related to dynamic release dates (the behaviour is not reproducable with fixed end dates). 

We've released 1.8.2 just now containing a fix for this - could you verify if this resolves the issue? Big thanks for uncovering this! 

Martin Suntinger, Product Manager for JIRA Portfolio

 

Thanks, this indeed resolve the issue. Sorry for the late reply.

Ran

Hi, I seem to be having the same problem. My plan is using only 36% of the team capacity and it is full of Gaps (empty sprints). The plan rolls out to 2018!

 

Can you help?

 

Thank you!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

132 views 9 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you