5 answers
Hi @Dinakaran R
For a readily available solution, to calculate the age of an issue, you might be interested in a mktplace app,
The "Time in Status" report with Status grouping feature, and the "Time between Statuses" report can help to meet your use case of calculating the issue age. Also the app has 20+ reports to meet a variety of use cases.
Disclaimer : I am part of the app team for this add-on
Hi @Dinakaran R ,
If you're looking to track issue age or custom SLA metrics in Jira, you can use the Custom Fields feature in the Time in Status app. It displays the time an issue has spent in its current status directly on the board and can be used in JQL. (Note: Only admins can create custom fields, and it's available for company-managed projects.)
To calculate the total age of an issue — not just the current status — you can generate a Time in Status report in the same app. The "Total" column will show the full issue age, and you can even create custom Status Groups to track specific workflow metrics.
(I’m part of the team that builds this app — feel free to reach out if you need help!)
Hi @Dinakaran R
That's an excellent question. Being able to sort issues by age or SLA status is a common and important goal. While a calculated custom field might seem like the direct solution, that approach can cause significant performance issues and data staleness, as the values don't update in real-time.
If you are keen to use a marketplace app, a more performant and reliable alternative is to use a reporting app that calculates this data on-demand. This ensures the information is always accurate when you view it, without continuously taxing your Jira system.
Our app, Timepiece - Time in Status for Jira, is built specifically for this purpose. It allows you to create dynamic reports for time-based metrics that directly address your requirements:
Sort by Age or SLA Time: You can generate a report showing real-time issue age or time spent in the current status. The key feature here is that you can simply click the column header to sort the entire list by that calculated time. This brings the oldest or most urgent issues to the top.
Live Views on Your Dashboard: Any report you create can be displayed in a Timepiece gadget on your Jira dashboard. This gives your team constant and immediate visibility of aging tickets or issues about to breach their SLA, right from your main workspace.
Highlight Critical Issues: To make urgent issues stand out even more, you can set thresholds to visually highlight them. For instance, any issue older than 7 days can be automatically colored red, making it impossible to miss during a quick scan.
Scheduled Reports & Alarms: Timepiece can also be configured to automatically email these reports on a schedule (e.g., daily or weekly) to keep stakeholders. Plus, you can set up Alarms to jump in only if your attention is needed.
To learn more about Timepiece - Time in Status for Jira, you can visit its Atlassian Marketplace page.
Disclosure: I am part of the team at OBSS that develops Timepiece. Please feel free if you have any question.
Hi @Dinakaran R,
a work item's (issue's) various lifecycle events and status changes are captured in an work item's work item history, which you can access from the work item view in Jira or via Jira's REST API. From these status changes, you can calculate the time that a work item has been in a particular status - however it can be quite tricky to do that by hand.
That's the reason why a lot of users rely on solutions from the Atlassian Marketplace to do that for them. E.g., you may want to have a look at 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 long list of so-called history columns that aren't natively available, including the time since creation, time in [status], time between [status] and [status], and many, many more.
This is how it looks in action:
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. Of course, you can also export your data to Excel or CSV in just two clicks.
Any questions just let me know,
Best,
Hannes
Hi @Dinakaran R,
Not sure if if is possible to add age as a field, but in JQL you try queries like these:
"Time to resolution" > 12h - for issues that took longer than 12h
created > startOfDay(-10) - for issues with age > 10 days
For something better, and if you want to try a plugin from Atlassian Marketplace, you can get a diagram and a report about the age of the issues by using the WIP Aging Chart gadget offered by our Great Gadgets app.
On its data tab, the report shows the issue by their age:
The same app offers also Control Chart gadget, Histogram Chart gadget and Time in Status gadget that you can use to track issues by SLA and easily identify SLA breaches.
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.