We have created a SLA (Jira Service Desk) that starts counting when an issue enters status #2 in the workflow and stops at status #4 or Resolved.
But when an issues is Resolved and then reopened - then it enters status #2 again - and the SLA is restarted (as if it is a new issue).
Is there any way that we can avoid this? So that once the SLA has stopped counting (not paused), then it cannot restart?
Try something like this. Use a label or similar qualification for reopened issues and exclude the label in your goals. Add the label (sla-exclusion) via a post function on reopen transition. The goal should look something like this:
....and labels != sla-exclusion...
I have not tried this but should work. You will need to consider potentially clearing the label if there are conditions where you would want to restart the sla after adding the label.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.