Our Service Desk has a "time to resolution" SLA. The SLA timer is configured to start on any of these 3 events:
The timer is configured to be paused on these 4 conditions:
But sometimes we see many tickets in Assigned status and the timer is paused.
If I take one of these issues and change the status to On Hold, and then change it back to Assigned, the timer still does not start back up again. When I look through issue history, none of the "Timer Stop" conditions were ever triggered on these issues either.
I have not figured out the pattern - some days it is fine and other days every 'Assigned' ticket I look at seems to have its timer paused.
I updated to the latest version of Service Desk on Tuesday but I am still seeing this issue. Any other ideas on what might cause this? What else should we be looking at?
What status are issues created in? There is an open bug with regards to time start vs pause precedence which may be the culprit. See the following bug record for details: https://jira.atlassian.com/browse/JSD-1524.
I've also seen issues where invalid SLA configuration can impact other metrics, specifically in cases where start and pause conditions are at odds. Do you have other SLAs configured?
Also, the start timer events appear redundant. The SLA timer starts at creation but also when assigned? Was this done for a particular reason?
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG