@Richard_Sather @Garrett_Knoll
‘Any task is marked as’ sounds great!
We can also detect ‘has subtasks’ or ‘not has subtask’ if this condition exists.
P.S.
I believe that ‘Any task is marked as’ is more useful than ‘All subtasks are marked as’.
2 Likes
This rule only works if All subtasks are marked as incomplete. There needs to be an option for if Any subtasks are marked incomplete. I have the rule you have stated above because it is better than nothing, but if a user was to mark just 1 of 5 subtasks as complete for example, the rule will not run.
As others have stated, I aslo think there should be a setting to force users to mark all subtasks as complete before a task can be marked as complete.
1 Like
We are also looking for a way to prevent users from marking a task as completed when it still has incomplete subtasks.
I tried to create a rule:
if a task is completed and all subtasks are completed –> complete the task (== do nothing),
otherwise –> mark task as incomplete.
However, this rule also prevents tasks with no subtasks from being marked as completed.
It’s encouraging to see that the team has acknowledged this issue and is discussing it internally.
Is there an estimated timeline for when it is expected to be resolved?
1 Like
As a part of our current Subtask improvement work (Subtask project inheritance and full tree view of all subtask levels within the List view), we will be improving Subtask support with Rules. But I’ve also flagged this with our new PM @Olha_Vintonik as something to consider for future roadmaps!
5 Likes