Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jira Gadget for Open Issues Age


Can anyone please suggest which two dimensional Jira Gadget to use for something like..reporting Issue Id on X Axis & Issue Age on Y Axis.

Please note ‘Average Age Report’ does not suffice our need.

Thanks in advance!

3 answers

1 accepted

2 votes
Answer accepted

Hi @Srilata Meka 

You need a field to display the issue age first, to then visualise this data on a dashboard gadget.

I've found a method to do this using Automation for Jira.


To do this, as a Jira Admin:

  1. Go to Jira Settings > Issues > Custom Fields
  2. Press the blue "Create Custom Field" button in the top-right
  3. Add a Number Field - and call it "Issue Age". You can add it to a screen - I chose not to so it wasn't visible / editable by users.
  4. Next, go to Automation. At a project-level, go to Project Settings > Automation - or for global rules, go to Jira Settings > System > Automation Rules
  5. Press the blue "Create Rule" button in the top-right
  6. For the Trigger, use "Scheduled" - schedule to run the rule once per day.
  7. On the same Trigger, check the "Run a JQL Search" box to TRUE, then enter appropriate JQL - eg. for a whole project, this might be project = ABC, or for only open issues, this might be project = ABC and resolution IS EMPTY. This is the set of issues the rule will run against.
  8. Next, add an Action - "Edit Issues" - choose to set your new custom field "Issue Age" - for the value enter: {{now.diff(issue.created).abs.days}}
  9. Give the rule a name and publish it
  10. Press the blue "Run Rule" button to populate the data immediately

^ This rule calculates the difference between the created date and today, providing a numeric value in the field.

You can then use this field in a dashboard gadget - for example, a Filter Results gadget, using a filter which looks for open issues. Select "Issue Age" as one of the columns.


A few additional notes:

  • Project Level: I would create this rule at a project-level. This is because you have virtually unlimited executions at this level. At global-level, you only receive 500 executions per product, per month - so you might end up utilising these quickly with this rule.
  • Text: If you want to display "XX days" rather than just a numeric value, create a "Text Field (Single Line)" on Step 3 instead - then in Step 8, enter the value as {{now.diff(issue.created).abs.days}} days
  • JQL Refinement / Lead Time: Consider refining the JQL in Step 7 if you have a large number of issues in your project - for example by issue type or, as seen above, including AND resolution IS EMPTY so the rule only runs on open issues. An added benefit to filtering for open issues is the field would also display lead time, as the count would stop at issue closure!
  • More Info: For more information on calculating values based on dates, see this page


Let us know if this works for you!


Jack Brickey Community Leader Aug 16, 2020


nice solution. One question, is this missing the part of only updating the Issue Age for open issues? Would you not want to add “AND status category != Done” in the JQL?

Hi @Stephen Wright _Elabor8_ 

Thank you for detailed response - I appreciate the time you took to explain the steps needed to be taken. I will give it a try and keep you posted.

Thank you,


Awesome @Srilata Meka - let us know how it goes!

@Jack Brickey - I actually did build it in a similar manner, I used AND resolution IS EMPTY

I left it off the original answer to give the choice of utilising the JQL best suited - but I think you're right, it makes sense to mention it (I've refined the wording). It would be beneficial if you have a large number of issues.

With this included you could also use "Issue Age" for both days since created and the lead time, as the count will stop after resolution has been set :)


Like Srilata Meka likes this

Thank you @Stephen Wright _Elabor8_ , the solution worked. I really appreciate how quickly you responded with a detailed solution.

Hi @Stephen Wright _Elabor8_ , The solution suggested by you had been working great for Project A. Now I am applying this 'Automation Rule' to all the existing projects in our Jira instance.

I updated the Scope of the Automation Rule to Global & ran the Rule. But Rule ran only on Project A.

I tried editing one of the 'Issue' from Project B and ran the rule, 'Issue age' was displayed only for this defect from Project B.

I tried updating the Scope to 'Multiple projects', updated even JQL query and ran the Rule. but still no luck.

Can you please let me know, what am I missing?

Any help would be greatly appreciated. Thank you ! 

Issue Rule.JPG

Hi @Stephen Wright _Elabor8_ , Thank you,  I am all set! 

Your initial response had the answer to my yesterday's question. I setup the automation rule at project level & am seeing the expected results.

This worked really well, however when I ran the automation it appears that when the "Issue Age" custom field was updated all subcribers and watchers of issues that met the JQL query received an email letting them know that the automation ran and the calculated value of the "Issue Age" field.  Is there a way to prevent updates to the new "Issue Age" field from triggering email updates to end users?

Hi @Leigh Elliott 

When creating the Action, you should be able to...

  • Open the More Options section
  • Ensure the Send Notifications? checkbox is set to OFF

^ I'd test this though, to see if it applies to subscribers/watchers. Let us know how you get on :)


Like Leigh Elliott likes this

Thanks Stephen, yes found this setting after creating the automation.  Forgot to update this post. It’s does work.

0 votes
Bloompeak Support Marketplace Partner Sep 18, 2022

Hi @Srilata Meka

As an alternative, 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.

  • 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 free solution, you can try the limited version Status Time Free.

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

0 votes

Hello @Srilata Meka

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center.  

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee

tisCloud_StatusDuration_LeadTime_with Estimates.png  tisCloud_AssigneeDuration.png     

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) 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.


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. It supports both Company Managed and Team Managed projects.

Time in Status 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.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
  • Export your data as XLS, XLSX, or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets


Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events