Perhaps it's due to being Monday morning, but during a review of my sechduling options, I decided to review the "Dependency Scheduling" section closely.
I can choose to either Rank a dependent item below a required item, or alternatively, Rank a required item above a dependent item.....
So, insofar as these two seem to be exactly the same option, I checked the specific documentation at https://confluence.atlassian.com/jiraportfolioserver/dependencies-schedule-844237026.html.
hmmm. Not enlightening at all, and clearly needs to be re-written --
I agree it's confusing, but they don't do the same thing exactly. Take the example of stories and dependencies from that page you linked.
If Rank dependent work item below required item is selected, it schedules it in the below order, even though it's not ranked that way:
So even though Story 1 is the 1st priority, it's scheduled below Story 4 since you said to rank the dependent item (Story 1) below the required item (Story 4). Since Story 4 is the 4th priority, Story 1 gets scheduled below it, in this case it is scheduled 4th.
If you select Rank required work item above dependent item, it does the opposite, and schedules it in this order:
In this case you're saying rank required item (Story 4) above dependent item (Story 1). Since Story 1 is the 1st priority, it schedules Story 4 above it.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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