in a project im working on, the SLAs are set according to the priority given to the issue.
The priority is set by a team than handles many tickets and the option for human error should be taken into account.
When a ticket is created with, say P1, the SLA is 3 hours. But, in those 3 hours, if an agent sees the ticket and decides that a priority should be different, say, P3, then the SLA should be update to 1.5D.
is it possible to have the SLA update if the field, upon which the SLA is based on, is updated? i've seen some questions and plugins around for restting the SLA which i thought of using as well for this.
Hi @ben friedman ,
If you want your SLA timer to reset and start counting from the beginning based on your goals for that priority, you can try Time to SLA
All you can do is select your priority on the priority field in the SLA configuration menu and enter priority as the SLA reset field.
After the initial setup, you can easily clone this SLA, change the SLA Goal and priority fields and save this new SLA.
You'll be up and running in no time!
If you don't use Time to SLa then when you change the priority, SLA will continue counting where it is originally started so for instance if 5 minutes has passed when the priority changes then 5 minutes will still be counted when you switch the priority which can be problematic.
You can also select different calculation methods such as Only First Cycle, Only Last Cycle and Largest Span with Time to SLA which then can be used to configure recurring SLAs.
Let me know if you have further questions.
Please note that I'm one of the folks behind Time to SLA so there might be other solutions out there and I might not be impartial
Hi @ben friedman ,
Perhaps i'm missing something but shouldn't this be working like you want by default?
For me when I have an SLA with 2 goals:
Priority = High: Goal 4h
Priority = Low: Goal 16h
and I change the priority my goal is changed as well on my issue for that SLA. The counter of course keeps running as it should be.. changing a goal should not reset your counter, otherwise it would be an easy trick to just circumvent the breach.
You might need to refresh your browser window to see it but the case you are describing to me (change of the goal but not resetting the counter) should just be the out of the box functionality.
Hello @ben friedman
You can try SLA Time and Report, which tracks the SLA status for each task.
Regarding your issue, you can set Priority #1 as a Start condition, where 2 and 3 priorities will be a Stop condition. Then Priority 2 configure as Start condition, but 1 and 3 as a Pause condition. This way when the Priority change, a timer will stop and the new one will be started.
I hope, it helps
Best regards, Mariana
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events