Earn badges and make progress
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
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
Rise up in the ranks
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Come for the products,
stay for the community
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
SLA breach A LOT. Condition: Is "Finish counting time when" --> "Resolution: set" enough for SLA?
Edited
Hi Expert Community of Jira,
My SLA - Time to Resolution is breached a lot, some of them is with 8000 hours or the like.
All of them are at the breached issues (61) are only on the last day/current day (see report picture below), and keeps being like that (e.g. only the last day will continue to show issues breached). This makes me theorize that some support issues do not get closed properly, so the Time to Resolution will breach. But when I look at some of the breached issues, they are categorized as "Done" and "Resolved".
I have a lot of conditions set on "finish counting time when...". This is might not be set right set right? (see picture below).
I tried to change the "finished time when..." condition to only "resolution: set" (keeping it simple), but it did not work.
My question:
What could it be? Something with workflow or the like?
I will provide extra pictures or explanation if needed.
Best
Andreas - Project adminitrator in Compant-managed project
1 answer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.