Like to check how long of each issue has been opened and show the day/time counts on a new custom field like "Age".
Is there a way to do that?
Thanks!
Hello @Licenses
Welcome to the Atlassian community.
Jira v9.12 does not have a native custom field that stores time as a duration.
If you have the Automation for Jira feature available to you (native in Data Center licensed instance) you could use an Automation Rule to get the duration difference between now() and createddate and store that in a field, but the value may not be in a pretty format such as 1d 3h 14m.
More information on that feature can be found in this documentation:
https://confluence.atlassian.com/automation0902/jira-data-center-automation-1431247381.html
If you are running on a Server license the Automation for Jira feature is not automatically included and would have needed to be installed by your Jira Administrators. It also may not have all the same functionality available in it as the feature set for a Data Center license.
If you are going to use Automation for Jira you will have to decide how often you want to update that "Age" field, and set the rule to trigger accordingly.
There are also third party apps available from the Atlassian Marketplace that can provide calculated fields for Time in Status and other duration types of metrics. However, if you are truly running under a Server license, support for Server has been ended and the app vendors no longer support getting new app licenses for Server environments. You would have to upgrade to a Data Center license to get a new app license.
Let me know if you have additional questions on the information I provided.
Hey @Licenses
Welcome to the Atlassian Community.
That's a very common request. While you can try to create a custom field and populate it using automation, it can be tricky to maintain and, most importantly, it won't work for your historical issues without running complex bulk updates.
Timepiece - Time in Status for Jira has a solution that calculates "Issue Age" instantly without needing a custom field.
You can use its Duration Between Statuses report for this.
It allows you to define a metric to measure the total time from the start of your workflow (Issue Creation) to the end (Done or Closed).
The best part is that you don't need a custom field to see this on the ticket. Timepiece adds a dedicated tab to your Issue View screen. You can open any issue and instantly see its "Age" (and other duration metrics) calculated precisely from your history.
Plus, it works retroactively for all your past issues from day one.
You can check Timepiece on the Atlassian Marketplace. Hope this helps you track your issue age easily.
Full disclosure: I'm on the team that makes Timepiece - Time in Status for Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Licenses - Welcome to the Atlassian Community!
There are a few ways to do this. One is to use a third-party app for Time In Status. There are several good ones at low cost or maybe even free.
The other way is create a custom number field and default it to 0. Then create an automation rule to increment the value of the field each day with a Scheduled trigger that runs in the middle of the night. Then each morning when you start work, you will know how long the work item has been open.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Licenses
Welcome to the community !!
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.
The app also has "Time in Field" report which can help the total time your issues spend in a particular field value.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Licenses ,
Yes – if you’re OK with using a Marketplace app, you can do this with Time in Status by SaaSJet (I’m part of the team that builds it).
!!! If you want to migrate to the Cloud, this solution may be useful.
Our app has Time in Status custom fields that let you show how long an issue has been open in a field like Age and display it right on the issue view or board card.
You can create a custom field that sums up the time an issue spends in selected statuses. For “Age”, you’d typically group all statuses except the final one (e.g. Done, Resolved), so you get the time from creation until completion.
Open the Time in Status Agile Board
On your project board, use the dropdown in the top-right and select Time in Status Agile Board.
Create a custom field (e.g. “Age”)
In the modal, enter a name like Age.
Select the working calendar you want to use (24/7 or only working hours).
Choose what to measure
Select Group statuses.
Add all statuses in your workflow except the last one (Done, Resolved, etc.).
This will give you the total time an issue spends “open” before it reaches the final state.
Add the custom field to your screens
Go to Jira settings → Work items → Custom fields.
Find your new field, select Associate to screen, then add it to the relevant screens.
Show it on the board
Open Board settings → Card layout.
Add your custom field so the Age value appears on the cards.
The field updates automatically (roughly every hour, and shortly after a status change or when the issue is opened).
Values are shown in dd:hh (days:hours).
You can also use this custom field in JQL to filter or sort issues by their age.
Note: Creating Time in Status custom fields requires Jira admin permissions and is available for company-managed boards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Licenses ,
Welcome to the community!
if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira. It has various "smart columns" you can easily add, including a "time in status" column that would solve your problem.
JXL is a full-fledged spreadsheet/table view for your Jira data that allows viewing, inline-editing, copy-pasting, sorting, and filtering by all your work items' fields, much like you’d do in e.g. Excel, Google Sheets, Smartsheet, or Airtable. It also comes with a long list of further features, including conditional formatting. With conditional formatting, you can define conditions on your work items - such as different due date ranges - and if these conditions are fulfilled, set the color of either the entire work item row or a particular cell. This is how it looks in action:
This is really just one of a virtually endless number of possible views and reports; you have full control over which data you want to show and highlight.
I should also add that conditional formatting plays nicely in combination with many other JXL features, such as configurable work item hierarchy, cascaded groupings by any fields, and sum-ups.
Any questions just let me know,
Best,
Lukas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Licenses welcome to the community
To add on what @John Funk and @Trudy Claspill have shared you can use Jira Service Management it has SLAs built in that will track this for you. It might be cheaper than a third-party app or automation depending on how many users need to see the SLA information. It also has built in reports that you can use to track how well you are doing on the SLAs. So if you have a metric that you would like to meet, example: all bugs need to be closed within 48hrs, it will let you know how many work items have breached that SLA.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.