nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

To find Resolution time (TAT) for JIRAs created

Balaji K M

I am creating jiras using multiple labels for multiple issues. I am creating a dashboard to have them all under a single dashboard. I need to find the turnaround time (time taken to close/resolve) of the jira. I have tried Resolution time, Average time in status, Average Age Chart gadgets but it is not working as expected. Any suggestions/help is much appreciated. Thanks!

Accepted answers

All comments

Bill Sheboy

Hi @Balaji K M -- Welcome to the Atlassian Community!

Would you please confirm your meaning of "Resolution time (TAT)"?

A couple of process flow measures which may be related are:

Lead Time: duration from request creation until completion. This is measured in calendar time.
Cycle Time: duration from two specific points in a process. For example, from start of work until completion. This is often measured in working hours.

If you want to measure either of those, you could use the built-in control chart, although it does have some limitations, leading teams to use marketplace addons instead.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/

Kind regards,
Bill

Valeriia_Havrylenko_SaaSJet

Hi @Balaji K M 👋

I suggest you to try Time in Status for Jira Cloud. Our add-on has a lot of possibilities for Jira reporting. We have 7 types of status time reports such as Time in Status, Assignee Time, Average Time. All the reports you can display as Pie, Bar or Area Charts.

Time in Status .png

Also you can get cycle and lead time to uncover bottlenecks and delays

Cycle_Time_in status.gif

I hope you like pizza, so here’s an example of how to distinguish Cycle and Lead time:

Знімок екрана 2023-12-19 о 17.39.11.png

All add-on reports are available in this gadget and you can control time in status data in the Issue List or Chart View.

Here is an Average Time report in the Chart View:

Знімок екрана 2023-12-19 о 17.19.17.png

Add-on has a 30-day free trial version and free up to 10 users.
Please, let me know if you have any questions

Hope it helps 😌

Amay Purohit_RVS

Hi @Balaji K M

Welcome to the Atlassian community !!

The OOTB reports provide limited results. If you are open for a mktplace app to get detailed reporting, you can take a look at the one we have built.

Time in Status Reports

You can track the time taken in each status for the issues with multiple types of reports, graphs , gadgets, status grouping and lot more. You can easily group your statuses via our app and find out the total resolution time for each ticket.

Disclaimer : I work for RVS, the vendor for this app

TIS - Cycle Time report.PNG

Balaji K M

Hey Bill! Thank you for your response. I want to pull a detailed report on the JIRAs that I create. That report should have the details on how many days/time it was taken to resolve/complete the request from the date of request creation.

Also, additional details like status duration i.e., time between each status change would helpful. Based on your response, I would think that the lead time and the cycle time would help me with my requirements. I would be looking into it.

Emre Toptancı [OBSS]

Hello @Balaji K M

Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. 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.

tisCloud_StatusDuration_LeadTime_with Estimates.png

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 customer 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 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.

Timepiece - Time in Status for Jira

EmreT

Bill Sheboy

Thank you for clarifying! The built-in control chart can usually supply those values, but on a chart rather than on a report for further analysis (e.g., trends, variability, etc.).

If you want to perform more analysis you would need one of these:

a marketplace addon for reporting or dashboard gadgets (as several of the vendors are already suggesting here)
for each issue, extract the changelog data with the REST API functions to analyze in another tool
use custom fields and automation rules to track the data, although this has limitations due to both the cost of running the rules and edge-cases like backward flow

Mehmet A _Bloompeak_

Hi @Balaji K M

Welcome to the Atlassian Community!

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. For further details, you can have a look at Status Time Reports How to Videos.

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 completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

unknown-hosting-type