nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira Gadget for Open Issues Age

Srilata Meka

Hi,

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!

Accepted answers

Ste Wright

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:

Go to Jira Settings > Issues > Custom Fields
Press the blue "Create Custom Field" button in the top-right
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.
Next, go to Automation. At a project-level, go to Project Settings > Automation - or for global rules, go to Jira Settings > System > Automation Rules
Press the blue "Create Rule" button in the top-right
For the Trigger, use "Scheduled" - schedule to run the rule once per day.
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.
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}}
Give the rule a name and publish it
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!

Ste

All comments

Ste Wright

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:

Go to Jira Settings > Issues > Custom Fields
Press the blue "Create Custom Field" button in the top-right
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.
Next, go to Automation. At a project-level, go to Project Settings > Automation - or for global rules, go to Jira Settings > System > Automation Rules
Press the blue "Create Rule" button in the top-right
For the Trigger, use "Scheduled" - schedule to run the rule once per day.
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.
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}}
Give the rule a name and publish it
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!

Ste

Jack Brickey

Stephen,

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?

Srilata Meka

Hi @Ste Wright

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,

Ste Wright

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

Ste

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

atl-orange