Task Relation "As Soon As Possible" Does Not Update Start Date Of Succeeding Task When Previous Task Finishes Early

[#1]

When task dependencies are set to "as soon as possible" and when a task finishes early, i.e. is set to 100% before planned completion date, the succeeding task is not moved forward to start right after that but stays on the previously "planned start date". In our opinion the succeeding task should be moved forward, when the previous task finishes early. This is why the task relation is set to "as soon as possible".

[#2]

I understand what you are describing, but my question is, should it change the Planned Start for the task that follows it? Does the Projected Start Date for the task that follows show that the task can now start ahead of schedule?

[#3]

Thanks for this comment. Let me clarify with the colleague who reported this to me. I am not sure he checked the Projected Start Date. I guess the confusion also arises as in the standard/default Views the Planned Start date is shown, not the Projected Start date. Best regards Tanja

[#4]

Thanks a lot for this hint! I did not get that when creating the ticket previously. The answer there was just that "it works as expected". So I asked the user to switch the View, e.g. "All Dates" and he confirmed that the Projected Start Date is adjusted if a predecessor task finishes early and the succeeding task has constraint "as soon as possible". Best regards Tanja

[#5]

This would be a nice add for projects when needed. It could be an additional task constraint that allows the tasks to adjust when needed. Some workers might not feel the sense of urgency to work on a task earlier but if the due date adjusts on the calendar automatically it will help them know it's time to GO!