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 Integrator
Queues are documented with filter criteria, dynamic per-agent queues, list, board and calendar views and JQL search, and SLAs are configured per project with goals defined as queries, pause conditions and business-hours calendars; queues can even be built around how close work sits to breaching an SLA. Escalation appears as manual, automatic and API on the higher plans. We found no public information on merge and split, skills- or load-based assignment, or first-response and resolution reporting by agent and queue, so the documented engine stops short of the top of the scale. 6 7 2