For Time to Acknowledge SLA, I forgot to add a status to Stop counting. I added that status to Stop counting, but an issue that had breached the SLA does not reflect the new SLAs. It still says the SLA is breached even though it should not have based on the new SLA rules. This issue is not Resolved/Closed.
The answer depends on which version of ServiceDesk you are running. On the current version, the SLA's will be updated/recalculated automatically. On older versions, you will need to click the "update" or "recalculate" link under the SLA menu on the left. This will take a minute, and refresh all SLA's within your project.
Be careful though. Each SLA metric goes through states running / paused / completed. Running means that the time counter is still making progress. Paused means that it is in an intermediate status like 'Waiting for Customer' or a time outside working hours. Completed means that the end state of your SLA metric has been reached.
Yes, SLA values will be recalculated automatically, but not on issues that have reached the end state of your SLA metrics. Those issues are considered to be complete with reference to that metric and their historic SLA times will as a result be kept by design.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs