Configure a ticket type’s priorities
Open Workspace Settings → Ticket Types, choose a ticket type, and expand its Priorities card. All Change subtypes share the Change priority settings, and all Custom subtypes share the Custom priority settings, just as they share statuses.
The five levels and their order are fixed. You cannot add or delete levels. All five levels remain available for manual and workflow assignments.
Turning off Selectable by AI prevents AI from assigning that level. People, workflows, and integrations can still select it. The card’s Set priority with AI header switch selects or clears all five levels for this ticket type. It stays synchronized with the row switches.
Write useful determinations
Describe impact and give concrete examples, such as: “Use when a service outage prevents more than ten employees from working and no workaround is available.” AI uses the descriptions for the ticket’s own type and can choose only levels marked as selectable by AI.Ticket views, filters, and SLAs
Tickets display the name configured for their type. Ticket-view filters show the distinct configured names across types with the corresponding level icons. Matching names at the same level share one filter option; different names remain separate. Existing saved level filters, sorting, and priority-based SLA criteria retain the underlying five levels. Renaming High does not change its rank or move it to another SLA priority level. When defining status transitions, priority choices use the names configured for that ticket type. Renaming a priority does not change which level an existing condition matches. See SLAs and Updating Ticket Properties.Changing ticket type
Reclassifying between Request and Incident preserves the underlying priority level. The matching level maps automatically even if its display name differs or AI selection is off. A type change never silently lowers or raises priority based on a renamed label.Promote priority settings
Priority configuration appears as one review resource per ticket type, such as Incident priorities. The review shows the five fixed levels and changes to their names, descriptions, and AI selection. Promotion maps by the fixed level, rather than a display name or a workspace-specific ID. Priority settings belong to the base ticket type and do not require a matching subtype or custom ticket type in the destination. Promoting settings does not rewrite existing ticket priorities.Workflows and the API
Priority IDs belong to a workspace and retain their identity across ticket types in that workspace. QueryGET /v2/priorities with the ticket’s teamId and ticketType to get the correct labels, descriptions, and AI settings.
When copying a workflow between workspaces, look up the destination workspace’s priorities and match the underlying level. Do not reuse a priority UUID from the source workspace. A nonexistent priority or a priority from another workspace returns an invalid-argument error.
Supply ticketType when updating priority configuration through the API. For compatibility, an older configuration update without a ticket type still changes that level’s name, description, or AI selection across the workspace’s types.
