There has to be a way to reset breached SLAs

[Tim Bonney]

Regarding: https://jira.atlassian.com/browse/JSDCLOUD-194

I find it hard to believe that this is not a larger issue for more users that this feature update, CREATED MORE THAN 12 YEARS AGO, still remains incomplete and listed for 'Future Consideration'!

If incorrectly breached SLAs, for any myriad of reasons is not an issue for other Admins out thee, I would LOVE to see how you all are handing it and whatever work around you all are implementing in order to reset them when breached in error.

Please share your solutions to this matter with me so that I can figure out how we can reset them when this happens. I have researched it and have attempted several workaround solutions through automation rules and configuration "tricks", but nothing has worked reliably and so I am reaching out to the community for some guidance.

Thanks in advance for any information you can share!

[Trudy Claspill]

Hello @Tim Bonney 

I found a reference to doing this with a third party app in this 2023 article:

The easiest way to Reset SLA in Jira Cloud