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

Why might an issue SLA timer be paused when issues don't meet any 'pause' criteria?

Britton Powers Sep 10, 2015

Our Service Desk has a "time to resolution" SLA. The SLA timer is configured to start on any of these 3 events:

  • Entered Status: Assigned
  • Issue Created
  • Resolution: Cleared

The timer is configured to be paused on these 4 conditions:

  • Status: On Hold
  • Status: Report Problem
  • Status: Request Cancellation
  • Status: Web Manager Queue

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?

2 answers

0 votes
Russ Gould Atlassian Team Sep 10, 2015

Hi Britton,

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?

Cheers,
Russ

 

0 votes
Britton Powers Sep 11, 2015

Would the timers on issues all show as "Paused" if the current time is outside service hours defined on the calendar? I think that's what is happening here. If so, I apologize for misunderstanding that.

Eugene Sokhransky Sep 21, 2015

Hi Britton, I had the same question and the calendars turned out to the be the reason. Outside of the working hours the issues are switched to paused.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Jira Service Desk

4 changes to queues and issues you don’t want to miss

Hello Atlassian Community! I'm Tania, a Senior Product Marketing Manager for Jira Service Desk Cloud! I'm excited to announce some exciting improvements coming up for those who work with queues and...

655 views 9 13
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