Urgent Scheduling Behavior : More detailed explanation

[amine benali]

Hello,

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 ? 

[Shannon S]

Hello Amine,

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:

• Estimates, and required skills and capacity
  
• Team schedules, e.g. working in either sprint iterations, or in a continuous flow of daily tasks
  
• Work stages, e.g. whether activities can happen either in parallel or in a specific sequence in the plan
  
• The sequence of work items, based on start and end release dates
  

• The ranking of work items in the backlog
  
• Dependencies between work items in the backlog
  
• Configurable constraints, e.g. how many people can work in parallel on a story
  
• The skills of each team member
  
• Availability of teams and people, taking into account holidays
  

 The following threads also have responses from Atlassian team members that explain the scheduling a bit further. Perhaps this will help?

• Solved: How does JIRA backlog order and portfolio rank influence each other? EDITED
• Epic ranking in Portfolio 2.0

Let us know if you have any questions!

Shannon