How to ensure Issue dependencies are displayed in correct order in scope pane of Portfolio?

Hi. I'm setting up my first Portfolio and have the Epics and Issues (Stories) displayed fine. Inside one Epic I have 2 issues that must be completed before the remaining stories (over 10) can be started. I have therefore created dependencies where the two issues "block" the remaining 10+. The problem I see is that when I recalculate the schedule the 2 issues are placed into a sprint after the 10+. i.e. In the wrong order. 

Is this expected behaviour? How can I ensure that the 2 issues that must come first are displayed and scheduled before the remaining 10?

1 answer

What do you have selected for your Dependency scheduling and Dependent story constraint fields in the configuration?  Click the three dot button next to the plan name and select Configure, then on the left select Scheduling.  And to confirm, you selected "Blocks" on the dependency popup for the 2 issues correct?

Thanks Steven. For Dependency scheduling I have "Rank dependent work item below required item" which I thought was correct, but happy to be corrected more :). Yes, the 2 issues which I want at the top have "blocks" against the items that must come after. Any help would be appreciated.

OK those settings seem correct.  Do you have fix versions explicitely selected for any of these issues in core JIRA?  That's the only other explanation I can think of, because it will always use that to schedule first, even if there are conflicting dependencies.  If you leave it to Portfolio to schedule everything on it's own it will do it correctly.  I would go through all of those individual issues and any parent or children for those issues and remove the fix version in core JIRA.  If you have any uncommitted changes for those issues in Portfolio, revert them.

Fix versions are not set. Checked them all. Have been playing around with the scheduling toggles and not getting much joy. It almost feels like the dependency needs to be set the other way around, which is the opposite to what we might see as intuitive.

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,064 views 6 19
Read article

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot