Ticket types
| Type | Use it for |
|---|---|
| Epic | A large body of work that groups stories, tasks and bugs. Can't belong to another epic. |
| Story | A user-facing piece of value. |
| Task | A unit of work. The default type. |
| Bug | Something broken. |
| Subtask | A step of another ticket. Created only from the parent with Add Subtask. |
Priorities
| Priority | Notes |
|---|---|
| Critical | The highest priority. Included in the High+ filter. |
| High | Included in the High+ filter. |
| Medium | The default. |
| Low | The lowest priority. |
Ticket keys
Each ticket gets a key made of the project code and a number that counts up across the whole project, for example TS-004-1, TS-004-2. Numbers are never reused, and keys are searchable.
Statuses
Ticket statuses are the board's workflow stages, so they can differ from board to board. A ticket counts as done when it's in the board's completion stage.