You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
we spent months trying to understand the scheduling logic of Portfolio based on the official documentations but still we don't understand the behavior based on the criteria as ranking, releases, dependencies.
Portfolio can still schedule items with high ranking (less important) before items with low ranking (more important).
we are at the point to stop using the tool because we cannot fully understand the scheduling !!!!
Can anyone from Atlassian help ?
From our article on Prioritizing Work Items:
Items that are ranked higher will be considered more important, and Portfolio will attempt to schedule them before lower ranked items.
Rank is not the only factor that defines the order. Have a look here: Scheduling Behavior
Portfolio for Jira uses the following factors to create a sensible schedule of your team's work items:
The following threads also have responses from Atlassian team members that explain the scheduling a bit further. Perhaps this will help?
Let us know if you have any questions!