SLA - First Business Resolution Metric
Asked by Kamlesh Panchal:

Hello,

Has anyone created a custom SLA for First Business Day Resolution?  

Idea is to capture how many % of tickets were resolved in first 24 hrs since ticket was created.

Regards,

Kamlesh


Answers:
author: Vitaly_Berezovsky_SaaSJet
body: Hi

I recommend an add-on [SLA Time and Report](https://marketplace.atlassian.com/apps/1220741/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_SLA-First-Business-Resolution-Metric_20240314) from the Atlassian Marketplace.

Steps to solve your problem in add-on:

First, add 24 hours to the goal deadline.

![](https://lh7-us.googleusercontent.com/yNxpF8B4wM3kwMhRkXOXjl6Bc9p_tqzbc_nnKk12thBcZuXgg5pXQ4GsOyGmKC2YMrwC8qcLzznRNGCIQeXiCwz6iTu8oSy2zpkPtf97IzCtez-2FMRhBSyNWYINQXtT9MBTrCC37JJ1_W6bSVlQRSk)

So now you can see broken SLAs on this dashboard.

![image.png](https://chat.google.com/u/0/api/get_attachment_url?url_type=FIFE_URL&content_type=image%2Fpng&attachment_token=AOo0EEX1hNCZ%2FV%2FZMEvNdre01pGeaDzzbc7uSF5HNwA2n9FS86OEedQ8WN6Fgct9RaXo8kMioZcOewQuOEOuCcp1uZwOpSIXHgeOyz%2BgidYmcTwJf05zdHMZvBM87G6cpKsfhYNnuJMuNkgeytrEGrqEOl7BESVptsF5sdEKdVSqfoksnGjp82WX%2B4azWb9f7wbknBi2Lhn208mZMD%2BsDyevNtZqULoWbPU6tPQEgroXSi2rSnBtRK2gLoMwvMBRjKTFZMnu%2FveMLTsLsvDi5uYXPQSNCAy4%2BgQY5mKWn%2BQREWKinIIWCvfEhCmgWigDTmFPD6Q9empA4GuT%2BsSFkzZDM0mU2s%2FJ23xKmHSWQWoknX8X8ZaIO8gAgJ%2F1Sg8ZM81cOv%2B3AZYXyVcSUxIP2cM17YWDdu2nPEjCJl1sbo9Pbs4bksZvCWKsI750jD47JnqFdG3n8qbgoZODM5MuNVyH5OCsApw3rOgk3X4BhzunN152H%2FbyqWNMvGHGUo783z8GluD%2FK%2FJ8ELINr9RLxfdFvhUzmEUo3Ok932X4N4qDR0RuxFUYFi0k9jhRA2Ba&sz=w512)

Next, you need to open the charts to see the percentage of tickets resolved in the first 24 hours after they were created.

![image.png](https://chat.google.com/u/0/api/get_attachment_url?url_type=FIFE_URL&content_type=image%2Fpng&attachment_token=AOo0EEW%2Bq4CoXxAjUnQunAGpgLhnD0HkTIsDG1OEAbGSzl4ET5qdDL8RAT%2Bmym2fsvYgNq6ayP86RQHV2Zqhpgn7ocrXhjMwASCg%2BV%2Fl%2Fddk3Hi8LxyGEvep97GFI4Ots0PKqzQWAW%2FSFic%2FmXCfSMoWkm096s4xISHwqtpRTK4SLepX9o3mD%2BGC5jq6HoELxlOCzJkUnlh%2BuT58fT7otlZeJw6rJb0NH9jhBwzfvdTLMghcQLyoMjvcLQv4zCarito7%2BDLVoCzJpH5c%2F9M3l5kOsbiMLZKBD3BwNVIHL9rDjaSYB9mzpDFKoxvhzE3ywFmlApOWRi1bLGygTvm8N7NP7d5HRBDL4Ln4DvLBhv%2B7bGlEX5xlUuLIqf1Fcz1kEMz06Fw6dPpjSxpZZlTQbQXKbDy418pEOnMln5s9UKiP9uU%2BUox1cb62IY6shJl1NIxYfiZyKML8q8wHHMh2jcriD%2Bc%2FD0SEiinrikX3p8M02p2uGPeQbJeV4jNt3VC1i32TkNmm2LbdDRGNCotnsFbgiE3RYlT2pJilI0FFufGBwtOX4%2Bmw7aOqaRe4rDI%3D&sz=w512)

Also, if you need, you can export this chart to EasyBI or other tools.

The application has a [30-day trial period](https://marketplace.atlassian.com/apps/1220741/?utm_source=Atlassian_Community&utm_medium=refferal&utm_campaign=Comment_SLA-First-Business-Resolution-Metric_20240314) and is free for small teams (up to 10 users), so you can check how well it suits you. My team developed it so our support team can help you with the settings.


author: Danut M _StonikByte_
body: Hi [@Kamlesh Panchal](/t5/user/viewprofilepage/user-id/5424170),

Try the gadgets offered by our [Great Gadgets](https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369) app, described in this article:

<https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369>

For this specific case, the **Histogram gadget** might be of great help for you. It shows the cycle time distribution for the tickets in a filter. Currently it displays the issue count in range, not the percentage, but could easily modify the gadget to display percentages.

![image.png](https://community.atlassian.com/t5/image/serverpage/image-id/311719i2FD76B277CC02A7F/image-size/large?v=v2&px=999 "image.png")

The app offers some other ways to display this info.

Hope this helps. If you have any questions for setting up these gadgets, please contact us at support@stonikbyte.com.

Danut.


author: Jack Brickey
body: Hi [@Kamlesh Panchal](/t5/user/viewprofilepage/user-id/5424170) , I have not done this for my own needs but certainly doable. Is your question about how to create the SLA or the reporting bit?

Example sla...

![IMG_3807.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/311522i6ACBB099F2C4EB98/image-size/large?v=v2&px=999 "IMG_3807.jpeg")

For reporting you could create a new report based upon the new SLA % met.

comments: author: Kamlesh Panchal
body: Hi Jack,

Thank you for your response.   
Yes, I am looking to set SLA only.   
Here's what I have defined.

![FDR1.png](https://community.atlassian.com/t5/image/serverpage/image-id/311526i149D9F977D63BA0D/image-size/large?v=v2&px=999 "FDR1.png")![FDR2.png](https://community.atlassian.com/t5/image/serverpage/image-id/311525iAD36F2D5BC7A628F/image-size/large?v=v2&px=999 "FDR2.png")


author: Jack Brickey
body: A couple of comments. First can you simplify the Goals to only have Highest using 24x7 calendar and everything else on the 9-5 calendar rather than listing out each priority? Secondly, what about issues reopened, is that a consideration. Personally I like using Resolution rather than Statuses.

with that said, what questions do you now have?


author: Kamlesh Panchal
body: Hi Jacky,

We have not kept option to reopen the ticket once it is marked as resolved.   
Also how would it impact if I specify goals for each priority instead of specifying as everything/all remaining?


author: Jack Brickey
body: You can keep the priorities, individually listed however, the goals are exactly the same so I'm not sure why you would go to that trouble. In other words, it appears that you want a 24 hour goal for all issues on a 9-to-5 calendar with the one exception being any issue with the highest priority in which case you want a 24 x 7 calendar.


author: Kamlesh Panchal
body: Perhaps, I feel there isn't any need for SLA I guess. All I need is to create a report that will return the # of tickets that are resolved within 24 hrs of ticket creation. Of course, it should honor the existing SLAs that I have defined (not the one mentioned before).


author: Jack Brickey
body: You could certainly create a daily report that reports on issues that were created AND resolved in the last 24h.

project = abc and resolution is not empty AND created \>= startofday(-1) AND created \< startofday()

give it a try.


author: Kamlesh Panchal
body: Hello Jacky, the provided query does return the tickets that were resolved within 24 hrs of its creation.   

However, I need to be able to find % of tickets of total resolved ticket that were resolved in first 24 hrs depending on the SLA.  

For example;

First Day Resolution = (Tickets resolved in 24 hrs / Total resolved tickets) \* 100.

How can I achieve this?


author: Jack Brickey
body: Hi [@Kamlesh Panchal](/t5/user/viewprofilepage/user-id/5424170) , your previous reply indicated "All I need is to create a report that will return the # of tickets that are resolved within 24 hrs of ticket creation.". This is why I offered the JQL report. as you found, it only provides a list of issues that were resolved within the same calendar day of being created.   

your most recent post indicates that indeed you need what you originally asked for which is a ++percentage++ of issues created in one day and resolved in that same day. To accomplish this either:

* use an SLA as previously discussed
* consider using a third-party ad on application
* consider using Excel or Google sheets. if you use sheets, you can automatically run your queries daily to populate a spreadsheet with calculations that you have created along with charts. Unfortunately with Excel, this is a manual daily routine.


Tags: cloud

jira-service-management

jira-service-management-cloud