Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

can i update an SLA that is already set for an issue?


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.   

4 answers

1 vote

Hi @ben friedman 

That is how SLA works. You can create SLA goals based on different priorities.

Just create a new goal for those priorities.


@Ravi Sagar _Adaptavist_ honored to have you answered :) ive been following your content online! :)

i can set a goal for each priority, but i want to be able to re-set it in case the priority updates. any suggestions?

Like Ravi Sagar _Adaptavist_ likes this

:) Happy to help. For reseting as mentioned by @Gokce Gursel _Snapbytes_  you can try Time to SLA.


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.

Screen Shot 2020-09-21 at 19.19.59.pngScreen Shot 2020-09-21 at 19.20.17.pngAfter the initial setup, you can easily clone this SLA, change the SLA Goal and priority fields and save this new SLA.

Screen Shot 2020-09-21 at 19.20.44.png

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.

Screen Shot 2020-09-21 at 19.25.02.png

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

sounds interesting! i'll give it a look.

Perfect! Let me know if you have any questions.



0 votes
Dirk Ronsmans Community Leader Sep 21, 2020

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.

  • @Dirk R_ that's wonderful news. Thats actually the best scenario for what i need. I didn't get to testing it yet as i figured, in my mind, that changing the priority wont update the goal. Thats a lesson to take forward... Thank you for your answer!
Like Dirk Ronsmans likes this

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

Issue Tab.jpg

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

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...

227 views 1 6
Read article

Community Events

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

Events near you