Status & workflow
Status means something different per workType. Based narrows the allowed values so the team stays aligned.
Tasks
Tasks have a fixed four-state workflow:
- todo β identified but not started
- in_progress β actively being worked on
- done β finished
- cancelled β no longer going to happen
The first transition to in_progress sets startDate (unless you set it manually). The last transition to done sets endDate. See Task timing.
Projects (bare)
- active β being worked on
- paused β not currently being worked on
- archived β set aside, no longer surfaced
Initiatives
- planned β defined, not yet started
- active β in flight
- shipped β DoD satisfied
- cancelled β abandoned
Milestones
- planned β defined, not yet started
- active β in flight
- done β DoD satisfied
- cancelled β abandoned
Milestones use done rather than shipped β there's no ship moment, just criteria met. Same shape as Initiative otherwise.
Workstreams
- active β the team is running this
- paused β temporarily not staffed
- archived β no longer an area of investment
Cycles
- upcoming β start date is in the future
- active β today is between start and end
- completed β end date has passed
Why narrow statuses matter
A status field that means anything ends up meaning nothing. By binding the allowed values to workType, Based guarantees that a board grouped by status is readable without translation β every column corresponds to a known state.
If you need more fine-grained tracking (e.g. βin review,β βblockedβ), use tags alongside status. See Assignees, priority & labels.