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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Auto-scheduling past due date



I have the following set of tasks (tracking my own tasks towards a project I am working on).


As you can see, the first highlighted task has an estimate of three days and the lowest priority. The second highlighted task has an estimate of one day and has a higher priority (2) and a due date of 08/Apr. However the auto-schedule algorithm for some reason doesn't give me the correct schedule. It just needs to give more priority to the second task and I will have what i want. 


Can someone explain what is going on? How do I force the scheduling algorithm to obey certain constraints about the start and end dates of a task? I know that the older UI had options to set earliest start/end date for tasks. I am looking for a way to enforce these in the new improved UI.




1 answer

Hi Aravind,


this is the normal behavior! The scheduler doesn't take the ranking into account with the highest priority. The ranking has some influence, but in case there are no further constraints like dependencies to other issues, it tries to schedule an issue as soon as possible considering the team capacity. This has some benefits, especially related to issues which are having other constraints like dependencies or fixed release start dates and are to be scheduled in the far future where the exact backlog sequence is not that important at the moment. So, you don't have to take care about the correct ranking at the moment, what you would have to do in case the scheduler would follow strictly the ranking.

But, this behavior has also some considerable disadvantages in the "near field", because as soon as the constraints are gone, e.g. blocking issues are closed, you observe the effect you see which causes then some troubles:

  1. Issues which are already in progress are suddenly are "overtaken" by not started  issues and are planned in the future
  2. In case you have, for whatever reasons (e.g. a delivery from outside your plan from another teams), to start in the future, you are not able to nail the date, which is an anchor for activities in your team down.

In the old interface (former Protfolio4JIRA, Live plans v2.x) you can work around these problems using the feature "Earlies Start Date" which prevents the scheduler to calculate an issue too early.

In the new planning interface (v3.x) this feature was removed. It is also killing for us!

There is a feature request to bring this feature back:

Please vote for it if you are interested in this feature.


Best regards,


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Admins, notify your Jira instance of system-wide changes with the new admin announcement banner

Hi All! We’re excited to share the launch of an announcement banner that lets Jira site administrators communicate directly to their users across their  Jira Cloud instance.  ...

609 views 15 18
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you