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

We use the "time to resolution" SLA with a weekday calendar (8:00 - 17:30). Any tickets raised outside these hours (17:31 - 07:59) the SLA clock stops and then starts again once it is in office hours.

How would I go about setting P1 and P2 tickets to ignore this SLA outside these hours (17:31 - 07:59). As right now if a ticket comes in at 18:00 and is a P1 or P2 the time to resolution clock is paused.


1 answer

1 accepted

3 votes
Answer accepted
Dirk Ronsmans
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 15, 2021

Hi @Laura Jackson ,

Each SLA has multiple SLA goals which are defined by a JQL. This JQL will tell the system which goal to use and then also the calendar behind that goal.

To have a different goal or calendar (or both) you will need to adjust the JQL in the existing goal(s) to exclude the P1 and P2 tickets (by adding something like Priority NOT IN ("P1","P2") )

and then create new goals with a 24/7 calendar and the correct JQL to include those P1,P2 priority tickets.

Thank you that worked :-)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events