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; } } }

How to Create a Jira Dashboard Widget for “Avg. Time to Resolve Bugs” (From Creation to Resolution)?

mohsen.nasiri@xentral.com

Hi Atlassian Community,

I am looking for a way to create a Jira dashboard gadget that displays the average (or even better more aggregation options) time it takes for bugs to be resolved—from the moment they are created to when they reach a resolution state (e.g., Done, Implemented, Released, or any other final resolution state). Ideally, I would like this to be visualized per day or week to track trends over time.

Current Setup:

1.We are using Jira Cloud.

2.We have the following apps installed:

• About Requirement Yogi

• ActionableAgile

• BigGantt

• Component Management

• Refined Sites

• Rich Filters

• Team Insights for Jira

• Worklogs

• Xray

• Zeplin for Jira Settings

What I Need Help With:

•Which Jira gadget or app can best accomplish this? Does Jira natively support this, or do I need an app like “Rich Filters” or “ActionableAgile” to achieve this view?

•What JQL filters or calculated fields do I need to create? Should I create a custom field to track resolution time?

•How do I set up the dashboard to visualize it by day or week? I want to track how long it takes for bugs to be resolved over time.

- Ideally it would be best if the solution is using the Rich Filter app's set of widgets since we are widely using that.

If you have experience setting this up or have suggestions on best practices, I’d really appreciate the help!

Thanks in advance.

Accepted answers

All comments

Marc -Devoteam-

Hi mohsen.nasiri@xentral.com

Welcome to the community.

This is not natively in Jira.

You could track this nu using automation. You will need a custom date/time field to store the result

Use smart values in automation, see jira-smart-values-date-and-time/#Date-difference

And use the creation date and resolved date as starting points.

This field can be used in filter results on a dashboard.

Otherwise look at the marketplace for apps, you could try multiple apps.

You could start with the app that is completely free, Status Time Reports Free - Time in Status"

Pasam Venkateshwarrao

Hi mohsen.nasiri@xentral.com

To simply get the issues "that were resolved in the last X hours" you can use a JQL like:

project = ABC and status = Resolved and status CHANGED TO Resolved AFTER -48h

If you want to see how long it took for issues to get resolved, you will need to use an SLA app or a reporting app.

In case you are OK with using a marketplace app, Time in Status app for this exact need. It is available for Jira Server, Cloud, and Data Center.

Iam using this app in my org

Thanks

Rahul_RVS

Hi mohsen.nasiri@xentral.com

Welcome to the community !!

To track time in status, as an alternative, you can try out

Time in Status Reports

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. You can also extract trends analysis and add that as a dashboard gadget too.

More details here.

Disclaimer : I am part of the app team for this add-on

TIS - WOW Resolution Time.PNG

Ayça Erdem_OBSS_

Hello mohsen.nasiri@xentral.com

Welcome to the community.

You can use Rich Filters to create calculated fields and visualize key metrics like average resolution time over time. With its time series gadget and filtering options, you can track trends and analyze performance based on different time frames.

However, if you ever need it I can recommend Timepiece -Time in Status for Jira , the oldest and leading "Time in Status" app in Atlassian Marketplace, which is built by my team at OBSS. It is available for Cloud, and Data Center.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee. In Status Duration Report you can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

Status Duration Consolidated Column.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 cycle time per kanban team 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.

Average Resolution Report.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.

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

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Ayça

Danut M _StonikByte_

Hi mohsen.nasiri@xentral.com,

As far as I know, Jira does not offer such gadget. There is Average Time in Status gadget that you could eventually try, but I don't think it will display what you need.

My advice is to search for an app on Atlassian Marketplace that offers such gadgets.

If you consider using an app, our Great Gadgets app offers multiple gadgets that you can use for tracking this. The best option for getting a trend chart is the Cycle Time Trend gadget, which allows you the average resolution per specified time intervals (weeks, months, etc) along with the overall average and trendline (linear or polynomial).

Optionally, the gadget can display a Data tab with a report showing the bugs and their resolution time. All you have to do is to configure the gadget with a filter/JQl that returns your bugs and to calculate the cycle as time between Issue Creation and entrance in a done-category status - no need for extra fields or other changes in Jira.

Very useful can be also the Cycle Time Trend Chart gadget, Histogram Chart gadget or Time in Status gadget offered by the same app.

See more details in this article: https://community.atlassian.com/t5/Jira-articles/Building-a-powerful-Kanban-dashboard-in-Jira-with-Great-Gadgets/ba-p/1664331

Danut.

Valeriia_Havrylenko_SaaSJet

Hi mohsen.nasiri@xentral.com
Welcome to the community!

If you're open to trying another app, I’d recommend Time Metrics Tracker | Time Between Statuses . It’s specifically designed to measure time metrics like Resolution Time—from issue creation to resolution—without requiring custom fields or complex JQL.

With Time Metrics Tracker, you can:
✅ Automatically calculate average resolution time for bugs.
✅ Visualize trends over days or weeks with built-in reports.
✅ Export data to Excel for deeper analysis.

Also you can book a session with our specialist to see add-on in action 🚀 Add-on developed by my by SaaSJet team.

Since you’re using Rich Filters, you might be able to configure some custom queries, but if you’re looking for an out-of-the-box solution, this app could be a great fit. Let me know if you’d like more details!

Hope this helps!

Margaux

Hi mohsen.nasiri@xentral.com!

I noticed that you have ActionableAgile Analytics installed! I'm Margaux, Head of Customer Experience at 55 Degrees and AAA is one of our products!

To analyze the cycle time for your bugs, you can use the Cycle Time Scatterplot chart. Simply load your data and apply a filter to only look at bugs. This will allow you to see how long your bugs take to complete. For example, you might observe that 85% of your bugs are resolved within 10 days or less.

One quick tip: Be cautious with averages, as they can sometimes hide valuable insights about outliers. Depending on the spread of your data, averages might not always give you the full picture.

Currently, we don’t have dashboard widgets available

Daniel Wester _55 Degrees_

Hi there,

I work with 55 Degrees (the folks building ActionableAgile). We actually have a Cycle time gadget in Jira cloud (see more at https://support.55degrees.se/space/ActionableAgile/1781923851/Cycle+Time+Summary+Gadget ).

We're also gearing up to have more gadgets coming soon where we'll be bringing more of the ActionableAgile charts/insights to Jira Dashboards. If you're interested in this - you can ping our Product Manager at julia@55degrees.se.

Thanks,

/Daniel

Mehmet A _Bloompeak_

Hi mohsen.nasiri@xentral.com

Welcome to the Atlassian Community!

As far as I understand, what you are looking for is a lead time (the time interval between the moment an issue is requested to the moment it is completed) report. The raw data you need is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to calculate lead time.

If you prefer using a marketplace app, 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 your case, you can have a look at Lead Time for Each Issue report. You can choose the statuses that you want to include in lead time calculation.

For further details, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

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

If you have any questions, feel free to schedule a call with us.

Hope it helps.

Kate C_

Hi @Pasam Venkateshwarrao - if you're part of a Marketplace App team, we recommend you follow the steps outlined here to get an 'Atlassian Partner' lozenge for your profile! Cheers!

Petru Simion [Simitech Ltd.]

Hi mohsen.nasiri@xentral.com ,

If you are open to using apps you can use Time in Status Dashboard for Jira , an app released by our company.

You can export to Excel and sum up all those statuses that are considered part of what you consider a cycle.

Regards,

Petru

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

rich-filter

resolution-time

bugs