Ticketing, queues & SLA
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.
3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.
5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.
8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Support Lead
Queues are documented in real depth — custom and dynamic queues, list, board and calendar views, filters by status, assignee and priority, and Jira Query Language search — and SLAs have JQL-defined goals, business-hours calendars, pause conditions and queues that surface work by how close it is to breaching. Escalation for major incidents is listed plan by plan. We found no public information on reporting of first-response and resolution time by agent or queue, macros, merge and split, or skills- or load-based assignment. 6 7 2