We would love to have some way to control or require a specific order to completing subtasks. While we can setup whole tasks with dependencies, we’re still unable to enforce a specific completion order in a list of subtasks. Like do subtask A first, then B, then C. We want our team to be unable to complete subsequent subtasks without completing the first one in the list first, then the second, then the third, and so on forth.
The idea is to add a new task type designation, either a “Cascade” or “Waterfall” task, in which all the subtasks of that task must be completed in order from top to bottom. The main task itself cannot be completed until all subtasks are done.
I don’t know if there is already a workaround or this has been requested before, though. Would be nice to have.