You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have a question regarding te behaviour of SLA met vs breached report.
In my project i have only one issue that breached on the 10th of december:
When accessig the SLA met vs breached report it doesn't show up that i had one issue that breached on the 10th :
Is this the expected behaviour ? Can anyone please explain to me the logic behind the report ?
Yes, it is expected behaviour. The moment your SLA is considered breached (and when a ticket appears on the report) is when the SLA timer stops. This was on December 11th.
The detail displayed in your first screenshot shows the time when your issue should have been resolved (or replied to, or anything else your SLA might be based on). But it didn't - it reached the end state of the SLA on the 11th and is listed on that date in your report.
Hope this helps!
Hello @Walter Buggenhout _ACA IT_ ,
Thank you for your response.
However the SLA timer is not stopped in the first screenshot, it's still ticking.
It didn't not reached the "end" state on the 11th, the status is still "open" and the clock is still running(time passed still increasing).
For me the report have to display something like this: