Does Jira support Age of a ticket after it has moved to certain status

[Sajal Mukherjee]

Hello team,

I am trying to create a report where we see time to resolve a issue after it has moved to certain status. For example, while the creation date of an issue can be any date, i want to get time stamp of the issue when it moved to second status and time stamp when it was resolved. Is there a way to track that? what would be the JQL for this query?

[Hannes Obweger - JXL for Jira]

Hi @Sajal Mukherjee

welcome to the community!

Just to add to Bill's great answer: If you're open to solutions from the Atlassian Marketplace, I think you'd like the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called history columns that aren’t natively available, including the time between [status] and [status].

With these, you can build a report like e.g. this in just a couple of clicks:

I've configured a Time between Investigation and Done column here, but you can configure any other status(es). As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes

[Bill Sheboy]

Hi @Sajal Mukherjee -- Welcome to the Atlassian Community!

The issue history tracks changes over time, including the transitions.  However that is not something that can be queried with out-of-the-box features of JQL.

Your work-arounds to see this time duration depend upon how often you need to do this, and willingness to spend money or perform additional work...

• need this one time
  • Review the issue history and manually calculate the time
• need this more often, and do not have money to spend
  • Try using the built-in control chart report, setting filtering and quick filters to adjust as needed.  There are several limitations / problems with that report, and so if it does not help...
  • Try adding custom fields and using automation rules to save the date / time of the issue transition and then perform the duration calculation when the issue is completed / resolved.
• need this often, and have money to spend
  • Investigate the Atlassian Marketplace for addon reporting tools for this type of measurement

Kind regards,
Bill

[Amay Purohit_RVS]

Hi @Sajal Mukherjee 

Welcome to  the community !!

If you are fine to try out a mktplace app, you can take a look at 

Time in Status Reports 

One of the many reports which the app provides is Time in Status in hours/days to determine , how much time the issue spent in each status in the complete lifecycle of the issue. The app has 20+ reports to track your bottleneck Issues & Processes.

Disclaimer : I work for the vendor who built this app

[Mehmet A _Bloompeak_]

Hi @Sajal Mukherjee

Welcome to the Atlassian Community!

Jira doesn't have a built-in solution for the reports you mentioned. 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.

• To get a report of status transition dates, you can have a look at Status Count And Entry Dates report. Entry date(see In Development, Ready for Testing, In Testing, In Development columns.) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.
• To get a report of how much time each assignee spent in each status, you can have a look at Time in Assignee report.

App Features:

• 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, resolution 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.

For further details, you can have a look at Status Time Reports How to Videos.

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

Hope it helps.

[Aron Gombas _Midori_]

When an issue is transitioned from status A to status B, it means that the value of the field "Status" changes from "A" to "B". And it is captured in the Change History of the issue.

If you want to effectively analyze it, you can export the issue history to Excel and filter the changes to only those where the field "status" was changed. It means that in Excel you should filter the spreadsheet rows to those where the column I equals to "status": 

Column N, I, K and L capture who, when changed the status from what old status to what new status. It is very intuitive.

[Gizem Gökçe _OBSS_]

Hello @Sajal Mukherjee ,

Welcome to the community!

Unfortunately, there is no way you can do this with standard JQL. In order to get the results that you desired you have to use a marketplace app. If you are ok to use a marketplace app for your reports, Timepiece - Time in Status for Jira which is developed by my team at OBSS, is the tool I would highly recommend. It is available for both Jira Cloud and Data Center.

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

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses by your choice to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. 

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses. This report type also allows the user to exclude the times for "pause" statuses.

   

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 developer 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. And the app has a REST API so you can get the reports from Jira UI or via REST. Also you can export the reports in to various formats easily. 

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features

Kind Regards,

Gizem

[Danut M _StonikByte_]

Hi @Sajal Mukherjee,

I'm afraid that you cannot do this by using Jira's default reports or gadgets. But fortunately, this can be easily done by using the gadgets offered by our Great Gadgets app. Here is the complete solution.

For example, you could configure the Cycle Time Control Chart gadget to calculate the cycle as duration between the entrance in your specific status and the moment when issue reached a done-category status (like Closed, Resolved or Done).

As a result, you will get a plot chart showing the issues based on their cycle time. You will be able to set a threshold, so that you can easily identify the issues that took longer than excepted.

This gadget offers also a Data tab with detailed report that you can export in CSV. 

 

  Similar to this, you could use Histogram Chart gadget and Cycle Time Trend chart gadget offered by the same app. See also: https://community.atlassian.com/t5/Jira-Software-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331

Hope this helps. 

Danut