You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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!
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:
^ 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:
Let us know if this works for 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 :)
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 !
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?
When creating the Action, you should be able to...
^ I'd test this though, to see if it applies to subscribers/watchers. Let us know how you get on :)
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.
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.
Hope it helps.
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.
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.
Using Time in Status you can: