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!


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
Community Members
Community Events
Community Groups

How to make Auto-schedule respect the tasks estimates?

Problem: Auto-schedule doesn't respect tasks estimates and not using available sprint capacity making the team not fully loaded.

I would like Auto-schedule to plan the tasks considering their estimation, team/sprint capacity and all the dependencies. So, I've created the plan for a dummy company-managed Scrum project like below.



Also, I've set up the team and project scheduling settings accordingly:2.png


However, it looks like Auto-schedule feature doesn't taking into account neither sprint/team capacity, nor the existing date values despite of selecting "Empty values only" for Sprint, Releases and Teams.

As a result, it suggests a plan of 6 sprints length instead of 1 sprint according to tasks estimates.



For better understanding here's how I expect the plan to look like (done manually):


1 answer

Hi @Ivan Klochkov,

There are many factors playing with the auto-scheduler function of advanced roadmaps. It is designed to take estimates and team capacity into account, but many other factors play a role as well.

This support article has a decent overview of all the things that impact the scheduler. There may be some clues in there as to why your suggested schedule comes out the way it does.

Hope this helps!

Hi @Walter Buggenhout _ACA IT_

Thanks for the hint! I've studied the article you had mentioned above, but it didn't help much as it doesn't explain how exactly the other factors affect the Auto-schedule logic.

I guess the problem lies somewhere in the logic of setting the duration of the task. For some reason, it reserves the entire duration of the sprint without paying attention to the estimate.

So, is there a setting that will allow Auto-schedule to include dependent tasks into one sprint, or it's a bug that needs to be reported?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events