Take slack time into account when rescheduling dependancies
T
Tadej Jevsevar
If you reschedule a task and there is sufficient slack time do not reschedule the dependent tasks.
(Submitted via User)
Log In
Brendan W
Merged in a post:
Autoscheduling of dependencies to take into account slack time
Gion Herren
the re-scheduling of dependent tasks should only begin once the previous task has used all the time allotted slack time before the next task.
As of now, the autoscheduling moves dependent tasks by the same amount, leading to a cascade that hurts the integrity of the data present in our projects.
We really want to use the autscheduling feature, but it should consider slack time before moving all tasks downstream.
Photo Viewer
View photos in a modal
K
Kyle Denny
It appears initial comment is from 2021. Almost 5 years and still no development. Completely agree with everyone hear. Slack time or float is one of the most important items when handling a project management schedule. Please implement or provide update.
Vincenzo Ursino
This is vitally important for us when we build a medium/large projects. Paramontly important and we wonder why this has been designed in such wrong way from a project management point of view!! Please, fix this ASAP...please!
J
Jagan S
+1 Need this feature. The easiest thing would be to make this a configurable option - so we can select if to use up slack or not.
Shaun Munro
This is vitally important for us when we build a large project. There is only one critical path generally and slack is built in throughout other parts. A task should be able to move within its given slack until it bumps up against it successor with out moving everything else downstream. I'm guessing clickup will have to support dependency lag to also make this work correctly.