Track the running age of an issue while it remains open?

[Soma Rohit]

In Jira Cloud, we currently see the age of a Bug or Work Request only after it is closed (created date to resolution date). Is there a way to display or track the running age of an issue while it remains open?

[Maria Reisinger]

Yes, Jira Cloud does let you track the running age of open issues — several ways to do it:

JQL — created < -30d AND resolution = Unresolved returns all open issues older than N days. Add statusCategory != Done if you don't use the resolution field consistently.

Issue Navigator — add "Created" as a visible column; Jira automatically shows "X days ago". Also useful: "Updated" and "Status Category Changed" to spot stale issues.

Board view — in Scrum/Kanban board settings → Card Layout you can expose "Created" on the card face. Kanban boards also show a built-in "Days in column" badge on cards.

Dashboard Gadgets — "Average Age Chart" and "Issues in Progress" both work on unresolved issues out of the box.

Automation — a scheduled daily rule can compute now - created and write the result into a number custom field called "Age (days)". That makes it sortable and filterable as a column everywhere in Jira.

Full disclosure: We're building MetaFrazo — an Operational Intelligence tool for Jira with built-in AI-driven answers for exactly these kinds of questions. No need to deal with cumbersome JQL statements. Launching Summer 2026.

[Marc -Devoteam-]

Hi @Soma Rohit 

Welcome to the community.

You could enable the following setting on a board, if the board is a kanban board.

Within the board setting on the card layou you can enable the option "Days in column", this displays based on coloured dots how long the issue is in a certain status.

Other option is to create a scheduled automation and in relation a custom field.

Run the automation on a scheduled basis and use smart values to get the time difference between created date and current dat and store this information in the custom field on the issue.

OR look at 3rd party solutions on the Atlassian marketplace.

[Rahul_RVS]

Hi @Soma Rohit 

Welcome to the community !!

If you would like to try out a mktplace app for this requirement, pls explore

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. It works for current issues and closed ones as well.

With Status grouping feature, can help you define your own cycle time / issue age time and view the averages of the same. Also the app has 20+ reports to meet a variety of use cases.

You can set your own working calendar to exclude weekends and holidays from the time in status calculation.

More details here.

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

[Danut M _StonikByte_]

Hi @Soma Rohit,

Welcome to the Atlassian Community!

I'm afraid that Jira’s out-of-the-box tools does not offer a good options here. 

A solution would be to look for a plugin on Atlassian Marketplace that is capable to provide this info. 

If you consider using a plugin, our Great Gadgets app offers a WIP Aging Chart gadget that can display the issues by their age. You can easily visualize the age, by hovering an issue in the chart.

You can choose for many age calculation methods, and it offers a Data tab with a list of issues and their age.  

Danut.

[Bartek Szajkowski _ Orbiscend OU]

Dear @Soma Rohit 

Hope my answer meets you well.

If you are open for the third-party app, I would like to recommend JQL ARGON app from Marketplace.

JQL ARGON Powerful Search 

ARGON Powerful JQL Search solves this directly. Its Time in Status custom field shows the running age of an issue live, not just after it's closed.

The timeInStatus function allows you to find issues that have spent a specific amount of time in a given status. This is useful for tracking how long issues remain in particular workflow states.

Example: Find Work Requests stuck In Progress longer than 2 weeks (no field needed)

issue > timeInStatus("project = SUPPORT AND issuetype = 'Work Request'", "In Progress", "2w")

There is much more combinations with TimeInStatus function.

I hope my answer will be useful for you.

Greetings

Bartek from Orbiscend OU (JQL Argon app provider)

[Birkan Yildiz _OBSS_]

Hey @Soma Rohit 

Welcome to the Community. 

If you are open to using 3rd party apps you can use Timepiece- Time in Status for Jira

You can track the real-time running age of an open issue using the Duration Between Statuses report in Timepiece.
You can easily select the Duration Between Statuses report type.
Click the Metrics button to define a custom metric. Set Start At to "Issue Creation" and Stop At to your final resolved or closed status. (No workflow update needed, and it works retrospectively.

In the report, look for the "Running" metric state. For issues that haven't reached the "Stop At" status yet, Timepiece displays a running man icon next to the value.

This "Running" metric continuously calculates the time from issue creation to the exact present moment, providing you with the live, running age of the issue while it remains open.

Alternatively, for a single issue, you can see the Issue Age in the Issue View Tab, too.

To learn more, you can visit Timepiece’s Atlassian Marketplace page.

Full disclosure, I'm on the team that makes Timepiece.

Best,
Birkan

[Anastasiia Maliei SaaSJet]

If you’re open to third-party apps, one option to consider is Time Metrics Tracker (built by my team).

It can be useful if you want to track open work as it ages, not only issues after they are resolved. For example, the WIP Run Chart helps show how long current in-progress issues have already been open, which can make it easier to notice items that may need attention before they are closed.

It can also provide more context than a simple age counter, since you can look at Time in Status, Blocked Time, Wait Time, and transition delays. That helps you see not only that an issue has been open for a while, but also where it may be getting stuck in the workflow.

So if your goal is to get better visibility into the running age of open work, a third-party app may be a good fit — especially if you want workflow-level insight, not just a created-to-today calculation.

[Khrystyna_Dzhus_SaaSJet_]

Hi @Soma Rohit 

Yes, you are right. In Jira Cloud, the “age” is usually calculated only after the issue is resolved. Therefore, it is not very helpful for tracking ongoing work.

If you need to see the running age of an issue while it’s still open, this usually requires using a third-party application.

For example, the Time in Status add-on (developed by my team) allows you to track the following:

• how long an issue has been open so far (up to the current moment) 

• how long it has been in a certain current status.

You can also group statuses (e.g. active vs waiting) to better understand where that time is actually spent. 

This makes it easier to monitor aging issues and identify those that are not closed for too long.

Happy to share more details if needed.