Every ticket has one kind (what it is), one state (where it is in its life), and one priority (how urgent it is). The workflow is the list of values they can take, and it is shared by every project and every board in the workspace. Owners and admins edit it under Settings → Workspace → Workflow and kinds, where each list opens with the same explanation and examples as below. There is no state machine: anyone who may change a ticket can move it from any state to any other. The workflow decides what the board columns are, which states count as closed, and where a ticket lands when it is reopened.
Before you start
You need the Owner or Admin role. Integrations can read the workflow with an API key, but changes are made in the browser only.
States
A state is where a ticket is in its life, and the column it sits in on every board: Backlog, To do, In progress, Review, Done in a new workspace. The States list is in board order: the first state is the leftmost column on every board. Each state has:
| Field | Meaning |
|---|---|
| Key | Lowercase letters, digits, underscores; starts with a letter; 2–32 characters. Fixed after creation. |
| Name | 1–60 characters. Can change at any time. |
| Category | Open or Closed. Moving a ticket into a closed state records when it closed; moving it back to an open state clears that. |
| Reopen target | Exactly one state is the reopen target, and it must be open. A ticket that comes back to life lands here. |
| Comment shortcut | Any number of states. A tagged state is offered as Comment + |
- Add state creates a state at the end of the list; use Move up and Move down to reorder.
- The reopen target cannot be re-categorised as closed and cannot be archived; pick another reopen target first.
- Archive is refused while tickets are in the state: "Move the tickets in this state elsewhere before archiving it."
Kinds
A kind is what a ticket is: a bug, a support request, a piece of planned work (Planning, Implementation, Bug, Support in a new workspace). It lets people tell support requests from planned work, and billing policies can differ per kind. Tickets that arrive by email or from client users get the inbound kind chosen under Rules. Kinds have a Key (fixed after creation) and a Name. Add kind appends one.
- The kind selected as Inbound kind cannot be archived: "This kind receives inbound email. Choose another inbound kind first."
- The last remaining kind cannot be archived: "A workspace needs at least one kind."
Kinds also carry the billing policy defaults per client and project; see Billing policies.
Priorities
A priority is how urgent a ticket is (No priority, Low, Medium, High, Urgent in a new workspace). The list is in board order, highest first: the priority at the top of the list sits at the top of every board column, the one at the bottom sits at the bottom, and tickets of the same priority are ordered by most recent update. The arrows move a priority one step up (more urgent) or down. The API returns the same list the other way round, lowest first. The lowest priority is shown without a badge on tickets unless it has a colour; the preview in Settings always shows it. Each priority has a Key (fixed), a Name, and a Colour; Add priority adds one at the top of the list as the new highest, without a colour; move it down with the arrows if it should rank lower. The colour picker offers No colour and eight swatches (green, yellow, orange, red, each soft or strong); the badge next to it shows the result. Without a colour, the two highest priorities are red and amber and the rest grey.
- The default priority cannot be archived: "This is the default priority. Choose another default first."
- A priority still used by tickets cannot be archived: "Tickets still use this priority. Change them before archiving it."
Rules
| Setting | Meaning | Constraint |
|---|---|---|
| Inbound kind | Assigned to tickets created from email and by client users. | Must be an active kind. |
| Customer-resolve state | The closed state a regular client user may move their own ticket to. Disabled turns this off. | Must be a closed state. Archiving that state resets the setting to Disabled. |
| Default priority | Given to new tickets from every door (form, email, API) when none is chosen. | Must be an active priority. |
| Reopen window (days) | An email reply to a closed ticket within this many days reopens it into the reopen target. | 0–365. Default 14. At 0, replies never reopen a ticket. |
A rule that has never been chosen shows Choose… instead of a value. Email cannot create tickets until the inbound kind, the default priority, and a reopen target are all set; a new workspace has all three from the start (see below).
The reopen window is also shown under Settings → Billing → Period and run settings.
What archiving does
Archiving a state, kind, or priority does one thing: it disappears from the pickers; existing tickets keep it. A ticket on an archived kind still shows that kind until someone changes it. Archived values are not deleted and keep their key, so the same key cannot be given to a new value.
Defaults in a new workspace
| List | Values |
|---|---|
| Kinds | Planning, Implementation, Bug, Support (inbound kind: Support) |
| States | Backlog (open, reopen target), To do, In progress (comment shortcut), Review, Done (closed, customer-resolve state, comment shortcut) |
| Priorities | No priority, Low, Medium (default), High, Urgent |
Rename them freely; the keys stay.
Common problems
"A state with this key exists." Keys are unique, including archived ones. Choose another key, or rename the existing state instead.
"The reopen target must be an open state." You tried to set a closed state as the reopen target, or to close the current one. Move the reopen target to an open state first.
A ticket reopened by itself. An email reply arrived inside the reopen window. Shorten the window or set it to 0.
Why can't a client user close their ticket? The customer-resolve state is Disabled, or the ticket was not started by them. Only a regular client user's own tickets can be moved there.