Breached SLA for a report
Asked by Dominik Ka?mierski:

Hello Atlassian community!

I need to track exact date and time of breached SLA and number of tickets with breached SLAs.

I would like to create a monthly report based on these.

I know that basic build-in option in JSM shows only tickets with currently breached SLAs and allows creating a report, but this is useless for us, because we need to have every breach under control with exact date and time of a breach.

Is it possible to create a custom field which would save a date of a breach and then create a report with use of this custom field?

Thank you!


Answers:
author: Jack Brickey
body: You could create a date field and set up an automation rule that triggers on breach and updates the breach date field with current date/time.

comments: author: Susan Waldrip
body: Following on what [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369) suggested, you could then create a filter using that field and subscribe to it to get a (printable) report.


author: Dominik Ka?mierski
body: Thank You both [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369) and [@Susan Waldrip](/t5/user/viewprofilepage/user-id/5343063)  
For every SLA I've created "SLA name breach" custom date field and populated it via Automation triggered by SLA breach. Then I created custom report in free plugin Jira Assistant.


author: Danut M _StonikByte_
body: Hi [@Dominik Ka?mierski](/t5/user/viewprofilepage/user-id/5507406),

Try this JQL filter for identifying the issues with breached SLA:

*"Time to resolution" = breached()*

Save this as a filter and then use it in the Filter Results gadget to list the issues with breached SLA.

Danut.

comments: author: Jack Brickey
body: But that won't show the exact time of breach. ?


author: Danut M _StonikByte_
body: [@Jack Brickey](/t5/user/viewprofilepage/user-id/853369) Indeed, but the breach time is the Creation time + SLA. So if the SLA is 1 day, if the issue was created on 18 Aug, then the breached SLA is 19 Aug. So, just displaying Creation time in the gadget could be helpful because it allows you to easily determine the SLA breached time. But, adding a date custom field as per your suggestion, like "SLA Breached", and setting it via automation to Creation Date + SLA and then adding it to the gadget will result in a complete report.


author: quentin_leroy
body: Hello [@Dominik Ka?mierski](/t5/user/viewprofilepage/user-id/5507406)

We might have a solution for you at Appfire!

[Reports and Timesheets for Jira](https://marketplace.atlassian.com/apps/1212942/reports-and-timesheets-for-jira) provides the ability to build [calculated fields](https://appfire.atlassian.net/wiki/spaces/ART/pages/65503476/Calculated+Fields+-+6.5.7#:~:text=Reports%20and%20Timesheets%20for%20Jira%20%2D%20Confluence&text=Calculated%20fields%20are%20fields%20built,meaningful%20data%20in%20the%20report.) and use custom fields in them. To show you how you could use the app in your specific use case, I have built a report using your requirements.

![Captura de pantalla 2024-08-16 a las 15.41.32.png](https://community.atlassian.com/t5/image/serverpage/image-id/342165i106BEA77AACC202B/image-size/large?v=v2&px=999 "Captura de pantalla 2024-08-16 a las 15.41.32.png")

In this case, I have use calculated fields to filter for Jira issues with breached SLAs, then created a report to provide a list of them.

![Captura de pantalla 2024-08-16 a las 15.45.47.png](https://community.atlassian.com/t5/image/serverpage/image-id/342166i45474AF681897A60/image-size/large?v=v2&px=999 "Captura de pantalla 2024-08-16 a las 15.45.47.png")

You can then drill down in each of the incident by clicking on the issue key and share the report with your collaborator through various channels or simply integrate it within your Jira dashboard.

Let me know if you have any questions.

Thanks!

comments: author: Dominik Ka?mierski
body: Hello [@quentin_leroy](/t5/user/viewprofilepage/user-id/5567078)  
Thank You for your answer but currently I'm not able to use paid plug-ins for this problem.


author: quentin_leroy
body: The application is free to use on a Jira instance with up to 10 users :) and glad to hear you found a workaround!


Tags: cloud

jira-cloud

jira-service-management

jira-service-management-cloud