Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,917
Community Members
 
Community Events
176
Community Groups

Urgent Scheduling Behavior : More detailed explanation

Edited

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 ? 

1 answer

0 votes
Shannon S Atlassian Team Jul 06, 2018

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?

Let us know if you have any questions!

Shannon

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events