Prevent automations from changing the status of dependent tasks if the dependent task is already completed

I have been using dependencies to show the relationship between tasks, and I have enabled the automation which will modify the status of dependent tasks when the parent is changed. But sometimes the automation will re-open tasks that are already complete!

The current automation is too rigid and assumes that all tasks are always completed in a linear fashion. But in reality I find that the order often changes as projects progress.

The automation needs to be enhanced so that you may define parameters about when the dependent tasks can be set. The main parameter that I would like to configure is:

  • When STATUS changes to COMPLETE, change the status of its DEPENDENT ON to WORKING ON IT unless DEPENDENT ON is COMPLETED

in this example, the dependent on status of ‘completed’ would refer to any status in the dependent on object that is defined as completed, and not necessarily a status named completed.

Alternatively it would be acceptable to use this logic

  • When STATUS changes to COMPLETE, change the status of its DEPENDENT ON to WORKING ON IT unless DEPENDENT ON is any of [COMPLETE, ABANDONED]

Without this change, I will need to choose between using automations and relying on dependency relationships. I don’t think I should need to choose and I hope others agree!