Looking for fancy reporting app for JSM DC
Asked by Sebastian Krzewi?ski:

Hi Community!

I'm looking for (probably) app which helps me to create report like below:

|----------|--------------------------|---------------------------|---------------------------------------------------|-----------------------------------------------|----------------------------------|------------------------------|
| Priority | No. of created incidents | No. of resolved incidents | No. of issues with time to first response SLA met | No. of issues with time to resolution SLA met | Time to first response SLA % met | Time to resolution SLA % met |
| P1       |                          |                           |                                                   |                                               |                                  |                              |
| P2       |                          |                           |                                                   |                                               |                                  |                              |

<br />

Maybe there is a better way to achieve this. I'm open to hear any useful solution!

Thanks!  
Seba


Answers:
author: quentin_leroy
body: Thank you [@Tomasz Kowalczyk](https://community.atlassian.com/t5/user/viewprofilepage/user-id/3784490) and [@Gorka Puente](/t5/user/viewprofilepage/user-id/3311956) for the mention.  

[@Sebastian Krzewi?ski](/t5/user/viewprofilepage/user-id/1561725) we might have the one solution for you at Appfire!

Using [Reports and Timesheets for Jira](https://marketplace.atlassian.com/apps/1212942/reports-and-timesheets-for-jira) you can use the SLAs functionality from Jira and the [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.) from the app to compile a single reports answering all your needs. I have created an example for you based on your requirements:

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

In this case, we can first create a simple subtraction to figure out the gap between the SLAs and the time an incident has spend in a specific status, in this case \`Time to first response\`.   

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

Then we want to know if this value is within the SLAs or not; hence we can use the \`GREATER THAN\` function to know if the \`Time to first response\` is greater than \`0\`.

If it is greater than 0, then it is within the SLAs. In contrary, if it is below 0, then the incidents is outside the SLAs.  
![Captura de pantalla 2024-08-16 a las 11.37.27.png](https://community.atlassian.com/t5/image/serverpage/image-id/342112iFF4DD0A8DA783EE9/image-size/large?v=v2&px=999 "Captura de pantalla 2024-08-16 a las 11.37.27.png")

To calculate the sum of issues meeting the SLAs, we can then use an \`IF ELSE\` function. In this case, IF time to first response meets the SLA, the calculated field will output a 1, if not a 0.

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

Finally, to calculate the percentage of incidents meeting the SLAs, we can simply use a \`DIVIDE\` function to divide the sum of issues answering the SLAs for first response by the total number of resolved incidents.

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

Hope this is helpful and will answer your needs. Do not hesitate to follow up if you have any questions.

You can download the app for free and try it for your specific use case before you commit. If you have any questions or need help along the way, we have a knowledgeable support team on stand by.

Thanks!


author: Danut M _StonikByte_
body: Hi [@Sebastian Krzewi?ski](/t5/user/viewprofilepage/user-id/1561725),

I think some of the numbers that you mentioned (created incidents and resolved incidents) can be displayed by using Issue Filter Statistic or Two Dimensional Filter Statistics gadgets of Jira.

But for the other calculations, indeed, an app is recommended because Jira does not provide such gadgets for complex calculations like yours.

You can search on Atlassian Marketplace for apps that does this type of calculations, but I'm afraid that there is no app to provide one single magical gadget able to display all these info; the solution is to use **multiple gadgets** for tracking those numbers.

A good app for addressing these needs is [Great Gadgets](https://marketplace.atlassian.com/search?query=great%20gadgets%20agile%20stonikbyte) app - an app developed by my team - that provides a suite of gadget that can help you track these numbers. Here is how:

* **No. of created incidents and No. of resolved incidents split by issue priority** - can be calculated by using**Pivot Table \& Pivot Chart gadget** and **Advanced Issue Filter Formula gadget**

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

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

* **No. of issues with time to first response SLA met** and **No. of issues with time to resolution SLA met** **-** can be calculated by using the**Histogram Chart gadget** but if you want to split it by priority you will need one gadget for each priority

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

I don't really understand the last two metrics (**Time to first response SLA % met** and **Time to resolution SLA % met**), it might be possible to calculate them by using the mentioned gadgets.

It might be possible that other gadgets of the same app to work for you case (**Issue Filter Formula gadget** or maybe **Control Chart gadget** for example). You can have a look over this community article that I wrote and see them all explained: [An effective dashboard for Service Desk and Customer Support teams in Jira Service Management](https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369)

Danut.


author: Tomasz Kowalczyk
body: Well, i think you can try to achieve this with Reports and Timesheets for Jira.

comments: author: Gorka Puente _Appfire_
body: You can certainly use [Reports and Timesheets](https://marketplace.atlassian.com/apps/1212942/reports-and-timesheets-for-jira?hosting=cloud&tab=overview) for doing this type of reports, my colleague Quentin is the PM for that product, thanks for the mention [@Tomasz Kowalczyk](/t5/user/viewprofilepage/user-id/3784490)

Another great alternative is [Dashboard Hub](https://marketplace.atlassian.com/apps/1223898/dashboard-hub-pro-charts-reports-time-in-status-tables?hosting=cloud&tab=overview), you can see some live examples of dashboards:

* [ITSM](https://ronindashboards-staging.herokuapp.com/jira/shared/dashboard?boardToken=VTJGc2RHVmtYMTkyY3J6andUcXo2M1Vwd25kaVVudUJsemZNS2FocVdvMnp5Vm1mY0VOejVpNE94WjVrUVNvZW1oZHRFd1BPUzE5ZVBMd2N6QW5UTHkxbURtd0FKQ3VtWnlOKzJNWXRiUnplVjRycVBrR1pSbXNPdG5qQ3ozR2FReEhBRnRiczZMOFRDank0NXJKam9VMVhlM3NwbHBNS1VUcjAxWVk2Vzg2UkpJa3F5WXc3MmtseVgvS3d6aE1uSTVEWmp4ZzhUVHQyc01WaVVEc3FWYjVGUllCbzJYdk5XWnQwTGtQUmtyMVdjK1FRVGtqVk9zVE40OE9SVGQ4dkJ1eGMvUFJROTh6Qnp4UmNaWExxV0l4aGlKQWNWVU53S1E3NW82SmwvQjg9)
* [Agile](https://ronindashboards-staging.herokuapp.com/jira/shared/dashboard?boardToken=VTJGc2RHVmtYMS9jZUN6VmZXeVNHWWZHQll0U05WMkhGOWNvQitOVFZFbEpuOGszWDFCT2ZEWWdGdmR5Rm1EK05XTEo1K1VBSXNMa1VuKzltYnRFNzdaMUlwam1ZRG1CYStZZlZmR3I4VnhCVU8yTzJnb2h1cksrM0cwaFM1MThhVXg2dGVCNktHOS9UVWloV3EwU2VhSkc4ZElpMUtvSmlkNFVQVTdoeVlZcERBSVprR1hxM0FJM1lxSjN1dXpOaWZxVXJTcTNXM3l5K3NDTXUxTVo4NlpYSGVEeHovaUFXRkxINlE0dVZmQlZwTHAvY1hpTUkvK1hMT0pydHZ0NU1OVG9SMzIrZUtMSm0wb3AvdnFYRmc9PQ%3D%3D)
* [DevOps](https://ronindashboards-staging.herokuapp.com/jira/shared/dashboard?boardToken=VTJGc2RHVmtYMTlOME9HaFBqdHI4UGpMQXdSTnhMNXo3d1FHdGxNNFZkWHZ4VlJQdE8zMldOOE9IZEo1dGc5cEozMUFMY0RhcFNIMTRUVUVOS0haT29UUUpubjBSK0pJMmVlZU1hZVM0VDhtYjR1b3EweEJhME5mYWpUbFlvREZNT3B2ZGtBMGV3M0Z2am1lUHlkdVRFQU01dm11YkphZmRjTkEvdnNwS3IzT1duYVphc0tMV3lNdFp2bjFkYnprdU1yYmw1SGFCb3NxUU1lMHMrQmhKYVdObFdoVk9tN2VoZWg3M2cyWXdHYkhLakt0eE1DbW85c3RpOVlVQTU5V3ZYcjRwdnNBaTZWeGVhYWFGbERLNlE9PQ%3D%3D)

Cheers!  


Tags: jira-service-management

jira-service-management-server

report

server