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; } } }

How can I produce a specific kind of aging report without add-ons

Phil Bustin_7fmhjs

We use a specific kind of aging report for an application from which we're migrating to Jira. The report shows the number of issues that were open (not resolved) from 1 to 7 days; 8 to 14 days; 15 to 27 days, and 28+ days.

The report we currently use (whose 4 totals are manually copied to the spreadsheet below) includes all issues--that means issues submitted before the calendar month, and issues submitted near the end of the month. It might be more useful to report just on issues submitted during the calendar month, or even just such issues that are closed, because an issue submitted the last day of the month is included in the count of issues that closed in one day.

Nevertheless, we need to report on or at least manually compile the four totals in Jira. How might we accomplish that?

Aging report.jpg

Accepted answers

Trudy P Claspill

Hello @Phil Bustin

There is not a native report that will support what you want. Jira search functionality does not support comparing one date field to another and deriving the difference as a criteria for selecting issues.

Without a third party app, the only method I can think of is for you to create a custom field in the issues to keep track of how many days an issue remained open. You could use an Automation Rule to populate the field.

All comments

Trudy P Claspill

Hello @Phil Bustin

Phil Bustin_7fmhjs

If I create a custom field and rule that increments a number each calendar day that an issue is unresolved, starting at the beginning of the calendar month; and resets it each calendar month, is there a simple report or other entity I can construct to show the totals for that month?

Trudy P Claspill

If you want to create a report of how many issues are in each category, then you might be able to do that with a different type of custom field.

The Two Dimensional Issue Statistics gadget on a Dashboard can be used to display total issue counts based on two stats (i.e. issue type and status). But each stat has to be a selection list of defined values. It can't be used to group items based on a generic numeric field.

If you make the custom field a Selection List (single select), and make the options represent the ranges you want to report, then you could use that in a Two Dimensional Statistics gadget.

Screen Shot 2023-03-06 at 11.50.15 AM.png

You automation would have to figure out which option to select rather than simply recording the number of days the issue had been open.

Phil Bustin_7fmhjs

Then, 4 single selection fields, each representing a range, and the automation to change the value when a counter field reached the appropriate value, or perhaps when a JQL value is reached.

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

jira-software-cloud