Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Auto-schedule lefts story points out of sprint that could be done

Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 10, 2020


I am hoping someone can give me a better understanding on how portfolio works. I have been testing it and it seems that the autoschedule always leaves story points out when they could fit in the capacity of the team or they choose one issues over others with no logic

In this example there is just one jira project, the team sprint velocity is 16 sp and all the issues are unassigned.

I do not understand why is giving priority to the issues 32 and 31 instead of 27. 27 Was created before and is in a release with a sooner target date. Before 32 and 31 where created it scheduled it in the next sprint but, after they were created is moving it later. Also the current configuration is:
2+2+5+1+3= 13 so it could fit more issues ( but there isn't one that would fit)
But if it did
5+5+1+3= 14 it could also fit one of the 2 sp issues 14+2=16, filling all the story points of the sprint!
So, any idea why it may be giving priority to the two issues with 2 sp instead of the issue that was created earlier.



1 answer

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 10, 2020

Hi @laralg ,


32 and 31 are ranked higher, which is a major factor in prioritisation here. That's the same rank as what you will see in your Sprint board or kanban board, what's on top is what's coming next.

You can find more on our ranking and scheduling in the following documentation pages:




Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events