Statuses, priorities and ticket types
Three small vocabularies do most of the organising in KAMI Tasks. Getting them straight — especially the difference between a status and a column — saves a lot of confusion.
Columns versus statuses
KAMI Tasks has six system columns, and they are the same in every project:
To Do · In Progress · Under Review · Done · On Hold · Blocked
These are what the Kanban board is built from, and what reports aggregate by.
On top of that, each project can define its own custom statuses — its own labels for stages of work — and map each one to a system column. A development project might run Not Started → In Discussion → In Progress → QA Testing → Pending Deploy → Resolved → Closed; a simpler project might use the system columns as-is.
The consequence to understand: several statuses can share one column. QA Testing and Pending Deploy can both map to Under Review, so filtering a report by column returns all of their tickets together. The status is the precise state; the column is the family it belongs to.
Custom statuses are set up per project in its settings — see Projects and access.
On Hold and Blocked are not the same
- On Hold — deliberately paused. Nobody is waiting; you chose to set it aside.
- Blocked — cannot proceed. Something or someone is in the way, and it needs unblocking, not patience.
Blocked tickets surface on My Work and can trigger automations — On Hold ones don't chase anyone. Use the one you mean.
Ticket types
| Type | Use it for |
|---|---|
| Epic | A large initiative that other tickets belong to |
| Story | A user-facing piece of work |
| Task | A concrete piece of work that isn't user-facing |
| Bug | Something broken |
| Improvement | Making something existing better |
| Subtask | A child step of another ticket |
Priorities
Trivial → Minor → Major → Critical → Blocker, in rising order of urgency.
Two of these do extra work: Critical tickets with no assignee can trigger an automation, and Blocker means exactly that — the sprint doesn't ship with this open. If everything is Critical, nothing is; keep the scale honest.