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
4,364,884
Community Members
 
Community Events
168
Community Groups

Issue Age Report

I need to create an exportable report that displays individual issue age based on the "change start date" that is selected for each. Any suggestions or prebuild reports that I could use to accomplish this? 

4 answers

0 votes
Rahul_RVS_Support Marketplace Partner Sep 19, 2022

Hi @Jordon Martig 

If you are fine with a mktplace app, for a readymade solution, you can try out our add-on to get this data.

The "Time in Status" report shows the time the issue was in each stage of its lifecycle.

 

Time in Status Reports 

The main features are as below

  • Multiple Time in Status Reports. Excel Export available for all status reports.
    • Time in Status
    • Time with Assignee
    • Time in Status with Assignee
    • Time with Assignee per Status
    • Status/Assignee Count
    • Multiple Transition Reports
    • Avg Time in status reports
    • Status Transition Dates Report
    • Time in Status Per Time Grain
    • Time with Assignee Per Time Grain
  • Status grouping
  • Save your reports
  • CSV Export
  • Multiple chart types
  • Dashboard GadgetTIS.PNG

 

0 votes
Bloompeak Support Marketplace Partner Sep 18, 2022

Hi @Jordon Martig

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 @Jordon Martig ,

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this 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.

Instead of working based on a given date, the app can display each status duration separately. This way, you move the issue to a "work started" status (or an equivalent status in your workflow) when the work actually starts and ignore the times before that. 

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.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

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

https://marketplace.atlassian.com/apps/1211756/

EmreT

0 votes

Hello @Jordon Martig 

Welcome to the community.

Is "change start date" a custom field that you have added to your issues?

One solution would be:

1. create another custom field named "age"

2. use an automation to set that field every time "change start date" is changed

3. use the issue search screen to retrieve the issues

4. set the output display to list view and include the "age" field in the columns

5. export the results.

It may be a custom field. It was available to me when creating this project. I'll give this a try and see how it works. thanks! 

@Trudy Claspill

I've got the custom field "age" added to my screen, but am stuck on the automation. I'd like the field age to count the days since the date selected in "Change start date." Any insight on how to accomplish this?  

Hello @Jordon Martig 

What have you got for your automation so far?

You'll need a trigger. I would select Field Value Changed and then pick you "Change start date" field.

Then you are going to need an Action. I would pick Edit Issue.

Pick the field you want to edit - "age".

You are going to need to use smart values to figure out the date difference between now() and the date in your custom field. This is a starting point for learning about smart values:

https://support.atlassian.com/cloud-automation/docs/what-are-smart-values/

And here is a page about working with smart values for dates and time. You should look at the "diff" function for getting the difference between two dates.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Capture.JPGhere is what I have so far. I would like this to recalc regularly so we can filter by the age of tickets. The "the change start date" selection should be stagnate once selected 

However, I can not get the rule to publish as I am getting this error: 

Capture.JPG

Oh, right, yes, sorry. What was I thinking? :-)

The components you've selected are correct, but the way you are trying to reference the "Change start date" field in the smart value is not correct.

Do you get an error in the audit log when the rule runs?

Look at the format of the diff function:

{{[date1].diff([date2]).[unit]}}

...and look at other examples where [date] is part of the format and an issue field is being referenced.

First you need to tell it that you want to reference a field in the issue that triggered the rule, so you start with

issue.

Then you have to tell it what field you want to reference. There are a few ways to reference a field; by name or by ID.

(issue.Change start date)

You might also want to insert Log Action actions to log the values of fields and calculations into your rule audit log, to see what values the rule is working with.

Trudy Claspill

Thank you for the help. I received an error after running the rule, but I'm not sure why because Day Count (or age as we were previously calling it) is set a numerical values with a defaultCapture.JPG of 1. 

@Jordon Martig 

I think you might have misunderstood my previous post. 

I was talking only about how you referenced the "Change start date" field within the smart value. You do still need the whole smart value with the diff function:

{{now.diff(issue.Change start date).days}}

You would get the error you saw if you are trying simply to assign the value of the "Change start date" field (a date picker field) to the Day Count field (a numeric field).

Oh! i did misunderstand! Let me give that a try and and see.

 

 

I do apricate all the help!

@Trudy Claspill ,

 

So the good news is that it appears to have worked. However, I got negative values. Thoughts? 

Capture.JPG

That is explained in the documentation. Take a closer look at it.

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events