Why does Portfolio appear to prioritise rank over release dates when calculating a schedule?

I am having a problem understanding scheduling decisions that Portfolio is making. It appears to take the issue's rank over any assigned release date and is therefore failing miserably to tell me whether we can make a particular release date or not. That could be my misconfiguration or a shortcoming in the tool. I'm looking for some pointers either way.

Here's my scenario:

  • I have a resonably populous backlog with an active sprint underway, culminating in a release at the end of August.
  • Most (if not all) of the issues in the current sprint are assigned to the August release.
  • I also have longer term issues in the backlog which are assigned to a December release.
  • Where appropriate, issues in both the August and December releases are assigned to certain individuals.
  • Some issues in the backlog are not yet assigned to a particular release - e.g. they may be roadmap items.
  • My August release is a cross project release which has a fixed end date of August.
  • My December release is a cross project release which starts ASAP and has a fixed end date of December.

If I calculate the schedule, Portfolio is scheduling some backlog issues which are assigned to the December release before items which are assigned to the August release, making the August release go late. The December assigned issues which are (wrongly in my view) being included in the August release appear to have a higher rank in the backlog.

Surely I don't have to re-order the whole backlog to get the scheduling to give me what I want to see? I.e. whether we can make the August and December dates in time, given the current scope? If I assign issues to the August release, surely I should expect Portfolio to try schedule them in before the defined end date of that release?

1 answer

Hi James.  I also find this to be a head-scratcher.  Did you ever figure out a way to just assign Issues to Releases, assign dates to Releases, and then have Portfolio re-rank the Issues dynamically based on Release Dates?    The scope of our releases/increments are very fluid right now, and I hate having to re-rank my Issues every time we decide to pull a feature in or defer another...

Hi Matt, no there's no breakthrough here I'm afraid. I had a support ticket open for a while and they acknowledged that this limitation was due to the way Portfolio performs its calculations. There's an open issue here you can vote for but I can't imagine a fix arriving any time soon.

https://jira.atlassian.com/browse/JPOSERVER-1911

Like you, I've been having to re-scrub my backlog so I can believe what Portfolio is telling me. 

Ok, thanks for the quick response and the link.  Guess we're in the same boat.  Good luck and take care!

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Jun 26, 2018 in Portfolio for Jira

New Portfolio for Jira Getting Started Guide

We've just launched a brand new guide to help you get started with Portfolio for Jira.  This guide is a companion piece to our new demo. The guide walks you through use-cases, best practices an...

259 views 7 4
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