How to report on how many tickets are resolved in a certain time period

[Danny.park]

Similar to created vs resolved report, I would like to see how long it takes for tickets to be closed in a certain time period.

For example, I want to see:

• x amount of tickets were closed within a day it was created
• x amount of tikcets were closed within a week it was created
• x amount of tikcets were closed within a month it was created

and so on. 

I've tried the following queries and it does't seem to be filtering out correctly when I manually review when it was created and how long it took to resolve:

• resolutiondate >= startOfDay(-7d) AND resolutiondate > startOfDay(-1d)
• resolutiondate >= startOfDay(-1d)
• resolutiondate >= startOfDay(-3d) AND resolutiondate <= endOfDay() AND created <= startOfDay(-3d)

[Valeriia_Havrylenko_SaaSJet]

Hello @Danny.park 

If you are OK to use add-ons, I guess you can try Time in Status  for Jira Cloud (developed by my SaaSJet team) with 7 types of status time reports to quickly analyze your work and improve processes. 



Some of them which can help you:

• Status Count,
• Transition Count,
• Time in Status per Date.

Our add-on has 30-day free trial version and free up to 10 users .

Please, let me know if you have any questions

Hope it helps, 

Valeriia 

[Joseph Chung Yin]

@Danny.park -

Welcome to the community -

You can try the following JQL -

• tickets closed on the same date when it was created -

project = <project key> and created >= startOfDay() and resolved <= endOfDay()

• tickets closed on the same week when it was created -

project = <project key> and created >= startOfWeek() and resolved <= endOfWeek()

• tickets closed on the same month when it was created - 

project = <project key> and created >= startOfMonth() and resolved <= endOfMonth()

Hope this helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Danny.park]

Thank you for your quick response! 

The limitation of the JQL you've shared is that it only shows for that day, week, or month. For example, project = <project key> and created >= startOfMonth() and resolved <= endOfMonth() only shows tickets for May.

Instead, what I would love to see is how many tickets were resolved for the past 1 day, 3 days, 7 days, 30 days, 30 days + and so on.

Would you be able to help with that? Thanks so much!

[Mehmet A _Bloompeak_]

Hi @Danny.park

Welcome to Atlassian Community!

You can get this report using Status Time Reports app (developed by our team) and MS Excel by following these steps:

1. After installing the app, create a "Lead Time for Each Issue Report" as described in this video. Lead Time column shows the time interval between the moment an issue is requested to the moment it is completed.
2. Get a CSV file export of your report and filter the issues in MS Excel according to your criteria.
   Count of issues with lead time less than 1 day => x amount of tickets were closed within a day it was created
   Count of Issues with lead time less than 7 days => x amount of tikcets were closed within a week it was created
   Count of Issues with lead time less than 30 days =>x amount of tikcets were closed within a month it was created

Here is the online demo link, you can see it in action and try without installing the app.

If you are looking for a free solution, you can try the limited version Status Time Free.

Hope it helps.

[Emre Toptancı _OBSS_]

Hello @Danny.park ,

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee. 

   

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per Vertical or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend. 

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company Managed and Team Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

  

https://marketplace.atlassian.com/apps/1211756/

EmreT