Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

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.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

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!

Leaderboard

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.

Atlassian Community about banner
4,458,177
Community Members
 
Community Events
176
Community Groups

Time to first reply/resolution time not being set

Edited

I'm monitoring first reply time/time to resolution SLA, but I have an issue where the times aren't being set on many tickets and thus the SLA Breached true/false flag is also not being set.

The Times are set on some tickets and this is correctly causing the SLA Breached flag to be set to true or false, but I can't see why there are so many with blank entries even for tickets that have a resolution and have been completed.

The Jira built in report that shows breached/vs met number is very very low because it's missing the tickets with 'blank' entries.

I've confirmed this by using PowerBi to do my own reports and I can see in the raw data that a high proportion of tickets that are resolved simply do not have any times set against them and have a blank SLA Breached field.

This means that resolved tickets are in a state of neither breached or not breached.

Does anyone know what could possibly cause this?

What trigger populates the first reply/resolution fields because that doesn't seem to be happening.

 

capture 3.PNGCapture 2.pngcapture 1.PNG

1 answer

1 accepted

0 votes
Answer accepted
Dave Mathijs Community Leader Jan 23, 2023

Hi @paul_creedy please share the goals and metrics of your SLA.

When does it start, pause, stop?

You may be onto something there because my SLA's are based of ticket priority and whether it's a service request or incident.  I don't have SLA's on low priority tickets, just medium, high, highest ones.

Looking at the raw data the tickets that don't have SLA fields set are ones with low and lowest priority.

So this seems to be the issue, there reason so many are blank is because there is no SLA trigger set for those ones due to the priority level of the ticket.  There is a catch all SLA but as there is no target time set against it, it will never trigger.

Your comment pointed me in right direction.

Like Dave Mathijs likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events