Hello
We discovered that SLA is configured wrong and we have alot of tickets which now considered breached where they are not actually breached. Is there is a way to fix this issue?
can we update the closed date? or a way to recalculate the SLA?
Early I used rest/servicedesk/1/servicedesk/sla/admin/task/destructive/reconstruct?force=true
But now I see that it don`t work at Cloud.
Do anybody have resolve?
To resolve the problem try SLA Time and Report. This add-on allows you to recalculate issues when the SLA configurations are changed or closed and re-count SLA time every time the user opens the page at all.
You can install add-on free for 30 days and set up the best SLA conditions for your Jira tickets.
This app is developed by my team, so I'll be happy to help you if you have questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, SLAs will not recalculate on closed issues. There are several feature requests that you can vote for here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.