I have an issue that did not breached sla, but it appears on issue search with the following query
The same occours with search breached()
When I forced a SLA recalculation (ex. modifying the SLA definition), it doesn´t appear anymore.
I couldn´t find out why this is happening.
Thanks in advance,
I am also having major issues with SLA and the breached status. I haven't found a proper existing bug report yet though, and I don't quite understand the issue very well yet.
However, what I do know is that some issues that are breached do NOT TRIGGER the breached query or event. Some issues that are not breached do trigger the breached query or event.
My reproduction rates are very low and I can't rule out custom configuration yet though. If I figure it out I'll post back here.
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot