Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,699
Community Members
 
Community Events
168
Community Groups

Create a view in that shows how many tickets older than a certain age have been closed recently

Edited

Requirement is to know how many tickets with more than 60 days resolved? 100 days, 150 days, 200 days resolved. It is to know how many tickets in each of these category of old tickets closed and how many are still pending.

For this need to create either graphical or tabled view in a Jira Dashboard.

5 answers

0 votes

Hello @Sunil Bharadwaj ,

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 and on each assignee

tisCloud_StatusDuration_LeadTime_with Estimates.png  tisCloud_AssigneeDuration.png     

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

Once you get the issue age value you need, you can filter issues based on these durations so you can get issues that were resolved in a time longer than x days.

tisCloud_StatusDuration_Filter.png

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 customer (organization) 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.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

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.

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.

And the app has a REST API so you can get the reports from Jira UI or via REST.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
  • Export your data as XLS, XLSX, or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets

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

EmreT

0 votes
Bloompeak Support Marketplace Partner Sep 25, 2022

Hi @Sunil Bharadwaj

You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

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

  • This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).
  • You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
  • Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
  • You can set different duration formats.
  • You can export reports in CSV file format and open them in MS Excel.
  • You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
  • You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

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

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

0 votes
Rahul_RVS_Support Marketplace Partner Sep 23, 2022

Hi @Sunil Bharadwaj 

If you are fine with a mktplace app, you can try out our add-on to get this data.

You can filter the issues which are in a particular status for more than certain days.

 

Time in Status Reports 

The main features are as below

  • Multiple Time in Status Reports. Excel Export available for all status reports.
    • Time in Status
    • Time with Assignee
    • Time in Status with Assignee
    • Time with Assignee per Status
    • Status/Assignee Count
    • Multiple Transition Reports
    • Avg Time in status reports
    • Status Transition Dates Report
    • Time in Status Per Time Grain
    • Time with Assignee Per Time Grain
  • Status grouping
  • Save your reports
  • CSV Export
  • Multiple chart types
  • Dashboard Gadget

TIs - Status Suration.PNG

0 votes
Rilwan Ahmed Community Leader Sep 23, 2022

Hi @Sunil Bharadwaj ,

There is no direct solution, but you need to play around below example and make use of < and > as necessary.
Make filters and add them to your dashboard so that you can get a compare view. 

  1. To know the tickets that were resolved in last 60 days, you can make use of JQL
    "resolutiondate > startOfDay(-60d)"
  2. To know the tickets which were created in last 60 days but not resolved, make use of JQL 
    "resolution is EMPTY AND createdDate > startOfDay(-60d) ORDER BY created ASC"
  3. To know the tickets which were created in last 60 days and is resolved, make use of JQL resolution is not EMPTY AND createdDate > startOfDay(-60d) ORDER BY created ASC
0 votes

So JQL does not support date compare, e.g. “resolutiondate > createdDate(+60). 

options:

  • use a daily scheduled automation rule along with a custom field to count the number of days that issue is open. The idea here is that every day and issues open that field will be incremented by one. Then you can use this field in your JQL define issues per your requirement
  • Consider an add-on application from the marketplace that does a better job of tracking time to resolution or improves on native JQL

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS

Atlassian Community Events