SLA targets can’t differ by priority within one queue
Setting different response times per priority means juggling multiple SLAs and queues instead of one clean rule.
The problem
Giving a Critical ticket a tighter target than a Low one inside the same queue is awkward in Jira Service Management, pushing teams into tangled SLA calendars and extra queues.
Who runs into this
Service desks that run priority-based response and resolution targets.
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.
Top community comments
We wrote a workaround script, but it breaks on every Jira update. Not sustainable.
744Our admins get complaints about this weekly. Adding our +1 and a link to our internal ticket.
710This should be classified as a bug, not a “suggestion”. It’s clearly broken behaviour.
367