nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Service Desk SLA clock problems

Drew Munson

We have two SLAs, on called "Time to first response" which is set to 8 hours and the other being "Time to resolution" which is set to 80 hours. Those times being for our most common, medium priority tickets. We also have our business hours set to 9 am - 5 pm EST.

Recently we have had some strange issues with our SLA clocks. One example is this:

We have also had instances where our sla clocks seem to have been continuing to run outside of our business hours. But both of these issues are intermittent.

Accepted answers

Drew Munson

Hi Victor,

Thank you for looking into this. It ended up being something that you could not have seen from these screenshots. The issue type, "Bugfix" was not one of the issue types defined by our SLA goals (it was a newly created issue type) so it was defaulting to some of the standard SLAs which are the 24 hrs to first response and 16 hrs to resolution.