Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to get the ageing of the jira defect based on the status

Pavan Thota iGTB
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 31, 2025

How to get the ageing of the jira defect based on the status
For example
JIRA status is moved from To Do to Analysis and then moved to Resolved
I want to know the how many days this defect is lying under resolved state

6 answers

3 votes
Rahul_RVS
Atlassian Partner
June 2, 2025

Hi @Pavan Thota iGTB 

Welcome to the community !!

If you would be interested in a mktplace solution to get issue time in status, you can try out our app.

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. The app has 20+ reports to meet a variety of use cases.

More details here.

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

TIS.png

2 votes
Iryna Menzheha_SaaSJet
Atlassian Partner
June 20, 2025

Hi @Pavan Thota iGTB  👋
Welcome to the Atlassian Community!

To get the ageing of a Jira defect based on status (e.g., how long it stayed in “Resolved”), here are your options:

1. Native Jira (Manual Method)

Jira doesn't provide built-in status-duration reports. But you can check manually:

  1. Open the issue.

  2. Go to the History tab.

  3. Find the timestamp when the status changed to Resolved and when it moved from Resolved (or stayed there).

  4. Calculate the duration manually.

Good for 1-2 issues
Not scalable for teams or bulk reporting

2. Alternative Solution - Time Metrics Tracker | Time Between Statuses.

If you want to track this across many issues, this app is purpose-built for it.

With Time Metrics Tracker | Time Between Statuses, you can:

  • 📐 Create a custom metric like:
    “Time in Resolved” → from first transition to Resolved to transition from Resolved (or current time if it’s still there).

Знімок екрана 2024-05-15 о 12.54.52.png

  • 📊 Visualize with charts:
    Histograms (to see distribution), tables (for exact time), or scatter plots (for outliers).

  • 📤 Export to Excel or CSV
    For in-depth SLA and defect analysis.

  • 📌 Add to Jira Dashboard with a gadget
    To track these metrics in real time.

App developed by my team.

Hope this helps!

2 votes
Ayça Erdem_OBSS_
Atlassian Partner
June 10, 2025

Hello @Pavan Thota iGTB 

Welcome to the community

You can get both the time a defect spent in a specific status (e.g. “Resolved”) and its overall Issue Age using Timepiece - Time in Status for Jira, the oldest and leading "Time in Status" app in the Atlassian Marketplace, which is developed by my team at OBSS. It is available for Jira Server, Cloud, and Data Center.

With the Status Duration Report, you can see how much time each issue spent in each individual status. This makes it easy to track how long a defect remained in a particular state like “Resolved,” “Analysis,” or any other part of your workflow.

In addition, you can calculate Issue Age  the total time from issue creation to now  by creating a Consolidated Column that sums durations across all open statuses. This gives you a live view of how long issues have been sitting unresolved or active in your backlog.

issueageconsolidatedcolumn.png

issueage_ConsolidatedColumnResult.png

 

 

For all numeric report types, Timepiece allows grouping by assignee, issue type, project, or even time periods such as created month or sprint — helping you track both detailed metrics and long-term trends.

The app works with existing Jira issue histories, so you don’t need to update workflows or add custom fields. Reports are available via the Timepiece reporting page, dashboard gadgets, issue view screen tabs, REST API, and can be exported in multiple formats.

If you'd like to explore this solution further, feel free to check out Timepiece - Time in Status and let me know if you need anything.

Hope it helps,
Ayça

2 votes
Piyush Annadate _ACE Pune_
Community Champion
June 1, 2025

Hello @Pavan Thota iGTB .
Welcome to the Community !
Ageing of a ticket is based on different case (A) From created to resolved (B) Time in status.
Unfortunately, there is no way you can find with native features, but you can achieve it with JQ

Just for Resolved state, you can calculate by having a custom field in number that would have an value as when it is moved to resolved state, then do a date different in days from RESOLVED - CREATED.

Also, there are add-on as mentioned here 

Also, you can eventually have some scripts written that would check the issue history/change log, get the status changes date and do calculations.

You can also check additional comments here 

1 vote
Mehmet A _Bloompeak_
Atlassian Partner
June 2, 2025

Hi @Pavan Thota iGTB

Welcome to the Atlassian Community!

Jira doesn't have a built-in solution for "time in status" info. 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.

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.

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

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.

App Features:

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

1 vote
Danut M _StonikByte_
Atlassian Partner
June 1, 2025

Hi @Pavan Thota iGTB,

Welcome to the Atlassian Community!

Curious about your use case... Why would you need to measure the time a bug lying under resolved state. Once a bug is resolved, you should not care about it.

As far as I know this cannot be measured by using the Jira's native gadgets and reports. So a solution would be to search for a plugin on Atlassian Marketplace. 

In case you want to try a plugin, you can easily measure this by using the Time in Status gadget offered by our Great Gadgets app.

All you have to do is to configure it with the JQL/filter that returns the bugs, and eventually choose to include only the Resolved status.

image.png

The gadget also displays a Data tab with the time in Resolved status for each issue, which you can easily export in CSV. 

image.png

Danut.

Suggest an answer

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

Atlassian Community Events