nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reset SLA on escalated request

Gabriel Viger_31lgu3

Hello everyone,

I was wondering if it is possible to reset an SLA if a ticket is escalated from P2 to P1 for example.

P1 = 15m time to first response

P2 = 1h Time to first response

The thing is that it shows that the SLA was breached because the Time to first response took 30 mins as it was created as a P2 but escalated to P1 afterwards.

Thanks for your input!

Gabriel

Accepted answers

All comments

Meg Holbrook

What field or transition are you using to indicate a P2 vs P2?

What you need to do is find the stop condition for the P1 and then create a new SLA for when the status (or other indicator) is set for the P2.

Meg Holbrook

P1 vs P2*

Gabriel Viger_31lgu3

Hi Meg,

I use the field priority to indicate the priority.

So here is my SLA for when a ticket is created as a P2:

Time to first response

Start: Issue Created

Stop: Comment: For Customers, Entered Status: Closed, Entered Status: In Progress, Entered Status: Not an issue, Entered Status: Under Analysis

And it targets this JQL:

project = ECS AND issuetype = "Bug eCom" AND priority = "02 - High"

Goal: 1h

For P1 tickets, it targets this JQL:

project = ECS AND issuetype = "Bug eCom" AND priority = "01 - Urgent"

Goal: 20m

This issue the team is having is when a ticket is created as a P2 but escalated as a P1 during the analysis process, it shows that the SLA was breached because a P2 SLA to TTFR is 1h and P1 SLA is 20m.

Maybe I created these SLAs the wrong also...

Thanks for your answer.

Gabriel

Meg Holbrook

Can you send a snip of your SLA? I'd like to take a look. I *think* I know the issue.