Sub-task stages keep multi-step work in order
Group sub-tasks into numbered stages so later work only starts once everything in the stage before it is finished.
Summary
Sub-tasks can now be grouped into numbered stages under their parent task. A stage acts as a checkpoint: work in a later stage only begins once every sub-task in the stage before it is actually finished, so a multi-step breakdown runs in the order you intended instead of all at once.
What You Gain
A task that breaks down into several steps — say, build the groundwork, then build on top of it, then polish — needs those steps to happen in order. Without a way to express that order, every sub-task was just one flat group, so there was no way to say "don't start step two until step one is genuinely done."
Picture a project with three stages: two sub-tasks to lay the groundwork, two to build the feature on top, and one to polish it. With stages, the two groundwork sub-tasks run first, and nothing in stage two is touched until both of those are complete — so you're never left reviewing work that was built on an unfinished foundation.
How It Works
- Sub-tasks can be grouped into any number of numbered stages under their shared parent.
- Sub-tasks left ungrouped behave exactly as before, counted as a single group.
- Later stages wait until every sub-task in an earlier stage is finished before anything in them starts.
- The current stage is visible on board cards, in sprint task rows, and inside the Task modal, so you can always see how far a breakdown has progressed.
Where to Find It
Sub-task stages are available on every project now — set them up when you break a task down into sub-tasks.
See what else shipped this month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.