Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

SLA timer rules question Edited



I know it might sound silly, but I'm not sure how SLA conditions working. For instance, see the sample on a picture:
Cauri - Service level agreements - Service project.png

In order to finish a counter, all 3 criteria should be met?

And if yes, then how I can configure a rule to finish the counter if any rule is complete?


The reason why I can't keep just 1 rule:

  • The client can raise a ticket, and before the agent reacted, either cancel or complete it by himself (i.e. resolution is set). So SLA 'Time to resolution' complete, but ''Time to first response' timer still ticking.
  • Another example: an agent replied to the customer 'Hey, we are on it' (no Resolution yet), and again -  ''Time to first response' still ticking. 


2 answers

1 accepted

1 vote
Answer accepted

@Dirk Ronsmansfo after hours of research case is solved thanks to Simon from Atlassian support assistance!

There is a bunch of bugs or limitations, here are the main takeaways:
- SLA 'Comment for: Customers' not working when an agent is considered as 'client' (e.i. he/she is a reporter and/or request participant and/or member of that organization).
- SLA 'Resolution Set' not working when dual resolution is made. For example, an automation/transition post function and manual add via resolve screen.

Workarounds and fixes:
- Try to avoid Resolution Set as an SLA trigger, Entered status: X is preferable.

- Here is the guide to re-run SLA timers after changes were made. Please note, in POST Url you need to add a parameter /reconstruct?force=TRUE, and Postman now a standalone app, not a Chrome extension app.

- Instruct agents to stay away from the client related fields and block clients to tag your agents as request participants (Project settings > Customer permissions > Sharing to only other customers within their organization).


Dirk Ronsmans Community Leader Apr 09, 2021

Thanks for providing the feedback!

1 vote
Dirk Ronsmans Community Leader Mar 30, 2021

Hi @Alexey ,

Actually no! The 3 finish conditions mean that any of those 3 will stop the timer.

Keep in mind this is a STOP condition, so if you go back to a START condition it will reset the timer and start counting from 0 again. (that is called a multi-cycle SLA).

@Dirk Ronsmansthanks for the fast reply!

Interesting, so any single condition from the list might stop the timer and I've set it correctly.

Nice tip about multi-cycle SLA, I might use it later somewhere, but my start condition is 'Issue Created', so I believe there is no way to trigger it again for the same request. 

I just got another 'bug' with SLA:

Full spec for Time for the first response:

SM Digital Holding - Service level agreements - Se.png

Full spec for Time to resolution:

SM Digital Holding - Service level agreements - Se (1).png

Results: Btw, it's still ticking!

[SM-26] Two BTC accounts without _ Update Balance_.png[SM-26] Two BTC accounts without _ Update Balance_ (1).png


Clearly, the request is closed, with resolution and visible comments. Agent reacted within 20 min and whole thing was solved after 27 minutes.


It's a bug or I did something wrong?

Hey @Alexey ,

As your STOP condition is "Resolution:set" in my opinion it should have stopped.

Your START conditions don't conflict with the STOP so it should be stopped.. or at least I don't see an issue with how your SLA is set up.

As you are on a Standard cloud plan, I would escalate that one to Atlassian directly on

Normally those Atlassian Engineers can view logs and see if maybe something is wrong with the environment itself. (it's not the first time that I've seen this..)

Would be great if they could confirm this as a bug.

I feel it has more to do with the Resolution:set than anything else. Just doesn't seem to be triggering.

As a workaround you could also add the statusses to your stop condition, Cancelled and Completed to see if it stops then.

@Dirk Ronsmanscontacted the support. Meanwhile, if you said that any condition from the list will STOP the timer, then none of them are working, including 'Comment: for customers'.

Oddly, but some JSM projects work fine and finish the timer as conditions are met.
All projects were cloned from one, including an SLA.

Dirk Ronsmans Community Leader Mar 30, 2021

Interesting, maybe it’s a big then when cloning? 
if you create a new SLA as a test with the same conditions, do those trigger then?

Any condition should stop the timer. That’s just a fact :) (unless all my SLA’s have always been wrong 😄) 

I’m curious to see what they come up with. 

Suggest an answer

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

Announcing Mindville Insight is now part of Jira Service Management!

Hello Community! We’re excited to announce that Mindville Insight’s asset and configuration management capabilities will now be integrated into Jira Service Management Premium and Enterprise plan...

751 views 12 15
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