What this screen is for
This is where the statuses used by the Projects module are configured. Tabs across the top select which kind of record you are editing statuses for, and the list beneath shows each status with its colour, its short slug, and badges marking it as the default, as a closing status, or as one built into the system.
Adding or editing a status takes a name, a colour, an icon, and two switches: whether it is the default for new records, and whether it counts as closed. Built-in statuses can be edited but not deleted.
Why it matters
The closed flag is the one to get right. Reports, filters and the "open projects" list all decide what is still live from that flag, not from the status name, so a status that means finished but is not marked as closing will keep its records counted as open.
What you see on this screen
Five tabs choose what you are editing statuses for: Tasks, Sprints, Stories, Projects and Milestones. Each row in the list beneath shows the status colour, its name, the short slug it is stored as, and up to three badges:
- Default — new records of that kind start at this status.
- Closed — records at this status count as finished.
- System — built in; it can be edited but not deleted.
Filters and actions
Add Status opens the form, which takes a Name, a Color as a picker or a hex code, an Icon from twelve choices, and two switches: Default and Marks as Closed. Deleting a status warns that items still using it may be left without one.
Status values
The sets shipped with the system, which you can rename and add to:
- Projects — active, completed, on hold, cancelled.
- Milestones — pending, in progress, completed, overdue.
- Tasks — to do, in progress, review, done.
- Sprints — new sprints start at planning; active marks the one currently running.
- Stories — new stories start at backlog.
Related
- All Projects — where the statuses appear as a filter
- Work Items — where work-item states are filtered and set