SLA targets can’t differ by priority within one queue
Give Critical a tighter target than Low without extra queues.
Different priorities deserve different response times. Here is how to do that with one clean SLA instead of a tangle.
The symptom
You want a Critical ticket answered faster than a Low one in the same queue, but configuring it pushes you into multiple overlapping SLAs and extra queues.
Why Jira Service Management behaves this way
A single SLA goal applies one target to everything that matches it. Varying the target by priority means stacking several goals with careful, brittle conditions.
The manual workaround — and why it falls short
Admins create a separate SLA (and often a separate queue) per priority and keep them all in sync by hand. It works until a calendar or holiday changes and one copy drifts.
How Patcher fixes it
Patcher lets a single SLA hold per-priority targets, so one rule covers Critical through Low without duplicating queues or calendars.
Turn it on
- Install Patcher for Jira Service Management from the Atlassian Marketplace.
- Open Patcher › Patches from your Jira Service Management admin.
- Find Per-priority SLA targets in the list and switch it on.
- Scope it to the projects you choose, then save — the fix is live immediately.