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!


Issues get same Start Date on same Assignee with "Auto-schedule"


We are converting to Advanced Roadmaps from the old Portfolio. But in our teem we see some change behavior regarding "Auto-schedule".

We have a lot of estimated issues (grouped in Epics) and when we use "Auto-schedule" a lot of issues (with the same assignee) and with estimates longer than a day, get the same "Start Date", as if the same person could work on multiple tasks at the same time.

Have others experienced the same and a way to fix it?

1 answer

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

Both the Start date and Due date are calculated simultaneously with the auto-scheduler which looks at the totality of all assigned work items and schedules for not just when they can be started and ended meaning that no 1 work item (issue) is scheduled independently and multiple items can start and the same date. The algorithm will account for the total days/hours needed and propose a Due date accordingly.

In scenarios where the work items should be scheduled individually and no 2 items should be worked on at the same time, this is where you would need to implement a dependency type of schedule which is done by adding Dependencies to the Issues so that one item cannot be started before completing the previous one and so forth which is what I believe would be ideal for your use case so that 2 issues can't have the same Start date.

But in our case the same assignee gets allocated way to much work on the same day(s). 

We have set ex. 6 hours working days, but the assignee can easily get assigned 50 hours of work which (according to auto-schedule) can be done in 4 days.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events