Workflows and statuses
Define the moves your process actually allows, and set the point at which work counts as stuck.
Statuses
Each project owns its statuses — the columns on its board. Edit them in Project → Settings → Statuses: rename, recolour, reorder, add and remove.
Each status has a category — To do, In progress, Done — which is how reports know what "completed" means. A status called "Shipped" only counts towards throughput if it is categorised as Done.
A status that tasks are currently in cannot be deleted. Move them first. The alternative — deleting the status and taking its tasks with it — is not a trade anyone would accept if asked.
Transitions
A workflow is the set of moves allowed between statuses. By default everything can go anywhere, which is right for most teams and wrong for some.
Restrict it when a move genuinely should not be possible — In review straight to Done without passing through QA, say. An attempted illegal move is refused and says what was and was not allowed, on the board and through the API alike.
Add restrictions only where somebody skipping a step causes a real problem. Every rule is also a rule people will work around by using the wrong status, and a workflow that gets gamed reports worse numbers than one that was never enforced.
Stuck work
Each status can carry a stale after threshold — the number of days a task may sit in it before Krrim treats it as stuck.
This is per status rather than per workspace, because the right answer differs enormously by column: three days in Input required is a fire, three days in Backlog is Tuesday.
Once past the threshold, a task:
- Shows a stuck badge
- Appears under
?stale=trueand on the stuck board - Starts the escalation ladder
The ladder
| Rung | Who is told | Repeats |
|---|---|---|
| 1 | The assignee | Daily |
| 2 | + the reporter and project lead | Daily |
| 3 | + project admins | Once |
The ladder terminates. After rung three, nobody is emailed about that task again — it stays visible on the stuck board and stops generating mail. A notification that arrives every day forever is one people filter, which removes the signal from every other escalation too.
Acknowledging or snoozing a nudge stops the reminders. It does not reset how long the task has been sitting there — the aging report still tells the truth about it, which is the whole point of having one.
Thresholds count calendar days, but emails are only sent on the working days you configure in Settings → Escalation. So a Friday threshold does not page somebody on Sunday.