nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Breached SLA Report

Dianne Clifford

Hi,

I'm looking to change the way we report on our time to resolution SLA and looking for some help.

The standard report in Jira Service Management only includes tickets on the report when they are resolved, which means there are open tickets that have breached our SLA that aren't included in the report. I'd like all tickets to be included in the report (open and resolved) in order for us to accurately report on the % of tickets we are achieving our SLA on.

Does anyone have a solution to this?

Thanks,
Dianne

Accepted answers

Gökçe Gürsel {Appfire}

Hi @Dianne Clifford ,

How about using SLA search functions in the Jira issue navigator and then exporting results?

TimetoResolution = isBreached() or everBreached() should work.

For more information, you can refer to the doc below.

https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/

Cheers,

Gökçe

Brant Schroeder

@Dianne Clifford

Any delivered report in service management can be edited. The series on a report are just created using JQL. If you click the edit button in the upper right hand corner of the report (You have to be a Project Admin to see this) you will then be able to edit the series and change the JQL to meet your requirements.

All comments

Gökçe Gürsel {Appfire}

Hi @Dianne Clifford ,

How about using SLA search functions in the Jira issue navigator and then exporting results?

TimetoResolution = isBreached() or everBreached() should work.

For more information, you can refer to the doc below.

https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/

Cheers,

Gökçe

Brant Schroeder

@Dianne Clifford

Dianne Clifford

Hi @Brant Schroeder

Thanks for your reply. I'm aware that the reports can be edited and customer JQL used however the problem with the reports is that the 'time to resolution' calculation works based off of the ticket being resolved. 'Resolved' is actually the only option available in the report (on the dropdown menu of the screen where you enter your custom JQL) so it doesn't give me what I need. I've since queried this with Atlassian too and they have advised that they only support tracking this based on tickets being resolved at this time.

However, I've managed to get a solution by installing a plug in that allows custom JQL to be used on a dashboard, so I can query the tickets that have breached our SLA, regardless of status.

Thanks again for your reply!

Dianne Clifford

Hi Gocke,

Thanks for your reply.

I've found a solution my adding a custom field to tickets that will populate the date/time a ticket breaches the SLA. And installed a plug in that allows custom JQL to be used on dashboards (as I found that even with the correct query, the report that comes standard with Jira Cloud for TTR still doesnt offer what I need)

Incase it's helpful to anyone else, this is a sample of the query I have used to get the results:
created >= 2021-05-04 AND created <= 2021-05-10 AND "Due date[Time stamp]" >= 2021-05-05 AND "Due date[Time stamp]" <= 2021-05-10

Many thanks
Dianne

Gökçe Gürsel {Appfire}

Great! I'm glad that you have resolved the issue.

Have a nice day!

Cheers,

Gökçe

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

report

sla

jira-service-management