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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

SLA сalculation according to Priority

LinkedIn (16).png

The importance or attention given to a ticket based on the SLA is known as priority. There are four priority levels by default: Low, Medium, High, and Highest. Low-priority tickets are the least important and do not require immediate attention, whereas "high-priority" tickets should be dealt with as quickly as possible.

It's a typical case that workflow has SLAs based on priorities. And they always have a chance to change priority during the issue solving. That means that the system should track them correctly: stop counting the initial SLA and start another one.

We here at SLA Time and Report suggest you create a few SLAs to cover every priority. Below you can find the screenshot of how SLA might look for a High priority issue with an 8-hours goal.

In our example, it starts if an issue has the status To Do and High priority. SLA will stop if the ticket moves to Done OR priority changes to another:


This 2nd condition is a key element here. The system will immediately stop tracking particular tasks with 8 hours limit and move to another SLA, which we have with 6 hours limit since it is Highest.


So, having such two SLAs, issues will be tracked according to the different time limits and no manual work is required.

The same thing you can do for downgrading your priority. Simply add it as an option for Stop condition.

If you'd like to restart the SLA timer, apply to the reset option. You can add different triggers, including priority to restart the SLA time calculation. For example, reset the timer if the priority is changed from Low to Highest.


Have you ever used priority as a condition for your SLAs? How did you manage the appropriate calculation?




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events