Since we've migrated our jira to cloud, i could realise the SLA Time to Resolution is always restarting when a ticket is reopened, However, this wasn't happening into the Jira Server.
I found something that might be the reason, although we had always the same configs, since the begining. In the workflow, it was made a config that when a ticket is reopened, the resolution will be cleared, as necessary to don't create any problem when searching for opened tickets.
But, when you look into the SLA configs, it was defined that the counting will start also when the resolution field be cleared,
Well, i would know please where we're making a mistake, and also how could we solve this, in order to when the next ticket be reopened, the SLA will keep counting where he was stopped, and not restarting again.
Hi @Felipe Dorocinski ,
That is indeed normal behavior that a SLA restarts with thsese START and STOP conditions.
The only way to fix this is to:
This way when you have a resolution set it will pause the timer (you will need to add a new STOP condition, like a Closed/Done status) and it will continue to count when the resolution is cleared aka no longer set.
That atleast is how I resolve this (without any addons)
This works like that to be able to do "multi cycle SLA's" which is normally not what you want for these..
If you already heard about Smart Commits in Bitbucket, know that you just stumbled upon something even better (and smarter!): Genius Commits by Better DevOps Automation for Jira Data Center (+ Server...
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