Steps are stored as an ordered array on the task itself, not as child rows. They do not schedule, remind or assign. The list row shows a done/total counter that turns green when complete; the counter carries over to the next occurrence of a recurring task with every step reset.
Also called: subtasks · steps · task checklist · 3 things I must not forget
- 1The client sends the whole checklist on every edit; the API keeps only well-formed rows, trims titles to 200 characters and caps at 30 steps.
- 2Edits save optimistically so the modal does not flicker per tick.
- 3When a recurring task is completed, its steps are copied to the next occurrence with done reset to false.
Migration 176 draws the line: subtasks are '[{id, title, done}] — a lightweight checklist INSIDE a task, not child rows. They don't schedule, remind, or assign; they're the "3 things I must not forget while doing this" list.' Making them real tasks would have doubled the list for no gain.
- Multi-step tasks either became five tasks or lost their detail
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →