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

Feature requests
,
1

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!

2

Totally agree this would be extremely useful as we’re encountering the same issue.

3

I wanted to add my name to the list who would like to see this feature. Or if the “custom automation” supported more of the features that are in templates so we were empowered to build this rule ourselves would work.

1 Like
4

Adding my name to this as well. Low votes, so adding name!
I’ve explained this now three times to my team as to why the “in progress” status has reverted to “ready”. Good for them for working ahead when possible—bad that the dependent status can’t keep up.

5

Since it seems this will never be fixed, i will add that I always add a second automation now.

IF status changes from [Completed] to [Working on It] set status to Completed

this will undo the changes from the dependency automation if they move a completed item back to an open status.