How is average age chart calculated?

Sarvesh Misra

Average age chart

Query 1 - Does jira consider all issue types which are present in the drop down while creating an issue --like Stories, Defects , implementation task , Request etc OR is it for just one of them )

Query 2 -Consider two issues below
Issue 1 :
1st Jan - Issue Created and maintained in backlog
5th Jan - Issue included in the sprint
10th Jan - Issue moved out of sprint back to backlog
15th Jan - Issue again pulled in the next sprint
20th Jan - Issue close

Issue 2 :
1st Jan - Issue Created and maintained in backlog
15th Jan - Issue included in the sprint
30th Jan - Issue moved out of sprint back to backlog
15th Feb - Issue again pulled in the next sprint
29th Feb - Issue close

What is the average age of the above two issues ?

Emre Toptancı [OBSS]

Hello Sarvesh,

Actually, Jira does not care about the status of issues. For Jira, an issue is unresolved as long as the Resolution system field is empty and it is resolved when a value is set for that field. 

The average age chart (or gadget) shows the average resolution time for the selected issues. For each day in the chart, it shows the average age of issues (since it was created) that were not resolved yet (that did not have a resolution value on that day). It includes ALL issues in your filter, does not select a specific type unless your filter does.

Average Age Chart (and gadget) offers a quick and easy start but provides limited insight with almost no flexibility. Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center.

Time in Status allows you to see how much time each issue spent on each status or assigned to each assignee as well as entry/exit dates for all statuses. You can also combine statuses into consolidated columns to see metrics like Issue Age, Cycle Time or Lead Time.

You can see the age for each issue individually or calculate averages and sums of those durations grouped by issue fields you select. (For example see the average Issue Age per project and per issuetype.)

You can produce reports based on the default 24/7 calendar or define your own business calendars with custom workdays and working hours. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

One feature that may be especially useful in your case is the History Trim function. This function allow you to prepare reports considering only a segment of issue histories. Since you move items from sprint to sprint, using this feature you can get separate reports showing issue status durations for only Sprint1 or only Sprint2.

All data can be exported as XLS, XLSX, CSV. The app introduces a REST API for accessing this data. All the report data can also be visualized by various chart types.

Timepiece - Time in Status for Jira

Emre Toptancı

OBSS