A priority ranks a ticket against the others. A new workspace has five, from lowest to highest: No priority, Low, Medium, High, and Urgent. Owners and Admins add, rename, reorder, and archive priorities under Settings → Workflow and kinds. The order is what matters: boards sort each column by priority, highest first, then by the most recently updated ticket.
How it relates to other concepts
- The default priority (Medium out of the box) is given to a new ticket from every door (the app, email, the API, MCP) when none is chosen.
- Priority is one of the triage-only fields: only workspace users, and elevated client users on the project, set it. A regular client user's choice is ignored.
- Priorities are independent of kind and state.
Rules
- The lowest priority renders no badge on cards and lists; every other priority shows its name.
- The default priority cannot be archived. Choose another default first.
- A priority that tickets still use cannot be archived. Change those tickets first.
- An archived priority disappears from the pickers; the order of the remaining ones is unchanged.
- Keys are fixed after creation; names are 1–60 characters.
- Lists can be filtered by one or more priorities; the ticket list itself is ordered by last update, not by priority.
Example
Acme renames "No priority" to "Someday" and keeps it lowest so those tickets sit quietly at the bottom of each column without a badge. Email tickets arrive as Medium; the person triaging raises a production outage to Urgent, and it jumps to the top of its column.