Reports showing high number of breached SLA's

Andrius Liugas

It has been raised that the reports for SLA's are not working properly.
For the current day it shows all the breaches that has happened in the space.
When its the next day, it will display all the breaches for that day but the stats for previous days are correct.

Has anyone experienced this?

Arkadiusz Wroblewski

Hi @Andrius Liugas

This is a known JSM reporting behavior. Previously breached SLAs with ongoing cycles can be counted against the current day, explaining the spike.

Atlassian documented this in JSDCLOUD-13459 (Closed Not a bug).

There's also a newer feature request, JSDCLOUD-18901 (Gathering Interest), to report breaches by their actual breach date.

As a workaround, you could filter your report to completed SLA cycles using "Time to resolution" = completed(), although this excludes ongoing breaches.

Best,

Arek🤠🧙‍♂️