I’ve recently started using Multi-Level Subtasks for managing large operational projects, and while the structure itself is powerful, I ran into a major limitation around rollup statuses and automations.
Current behavior:
All subtasks can be completed
The rollup status becomes fully green ('Done')
But the parent item is still not considered “Done” from an automation perspective
Which means:
automations don’t trigger properly,
parent items don’t move automatically to DONE groups,
and users are forced into manual maintenance or complicated workaround automations.
Another challenge:
In real workflows, “Done” is not always the only valid completion state.
Sometimes subtasks may end as:
Done
Canceled
Not Needed
And those should still allow the parent item to be considered completed.
Would love to see:
rollup statuses behave like real automation triggers,
native “all subtasks completed” logic,
configurable completion states,
and less dependency on workaround columns and mirroring logic.
Curious if others managing large operational boards are running into the same limitations.