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

[Phil Bustin]

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?

[Trudy Claspill · Accepted solution]

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.

[Phil Bustin]

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 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.

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]

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.

[Trudy Claspill]

I don't think you need 4 single select fields. You need one Single Select field with 4 options; one option for each range.

In your rule you could then get the difference between the Created field and the Resolved field in days, and based on that set the value of the Single Select field to the appropriate range/option.

[Phil Bustin]

Sounds great.  I anticipate trying it in a week or so.

[Danno]

@Trudy Claspill and @Phil Bustin I'm glad I stumbled onto this post. I just got asked to provide the same thing for one issuetype. I think I got the jist of your suggestion Trudy so I will see if I get it right first before asking for clarification.

[Danno]

@Trudy Claspill I've got this automation and report working somewhat. I seem to be having trouble with the automation not processing some of the tickets that are included in the initial search in the trigger and the same search in a lookup issues action.

The search in the lookup Issues validates to a filter I am using to find every open "Discrepancy Report" which returns 84 issues. Below are issues that do not get updated.  The issues that have the blank space in the far right column do not get processed for some reason which has me baffled. It's not an editing permission for the project since it has processed some of them. Any suggestions?

[Trudy Claspill]

Hello @Danno 

Could you please start a new Question post to get help with your issue? The only people who will see your question within this post are people who are already involved in this post or are Watching this post. Starting a new Question will make it visible to a wider group.

Mention this Question (with a link) in your new Question post so people can find the background information.

Show the complete automation rule, the details of each step in your automation, and also show the Audit Log for the rule execution.