Statuses
Every initiative, bug, and todo has a status that shows where it is in its lifecycle.
Statuses
| Status | Meaning |
|---|---|
| Idea | Early concept or intake item that still needs shaping. |
| Open | Work exists, but has not been selected for active planning. |
| Planned | Approved or selected for upcoming work. |
| In Progress | Someone is actively working on it. |
| Review | Waiting for review, triage, or human confirmation. |
| Blocked | Waiting on a dependency, decision, missing input, or external issue. |
| Completed | Finished and included in history, recaps, and analytics. |
| Merged | Code work has been merged. |
| Cancelled | Closed without continuing in its current form. |
| Duplicate | Closed because another work item already represents it. |
Initiatives with children
Completed and Cancelled are final. When you change the status of a parent initiative, child initiatives that are already completed or cancelled keep their status.
Priorities
Each item can also have a priority. Issues synced from Jira or Linear keep the priority set there.
Issue priorities
| Priority | Meaning |
|---|---|
Critical | Highest severity work that needs immediate attention. |
Urgent | Time-sensitive work that should interrupt normal ordering. |
High | Important work that should be handled before the default queue. |
Medium | Normal priority work. |
Low | Useful work that can wait behind higher-impact items. |
Lowest | Low-impact work to keep visible without crowding current planning. |
Statuses drive what appears in triage, on boards, and in recaps.