Average Age Chart Appears to not correlate for our reporting
Asked by George Abdo:

Hi All,

I am using the average age chart to report on our service desk tickets.

The filter I am using has the following:

Project="Service Desk" and created \>= -52w AND Resolved \>= -52w AND assignee in ("service desk group")

So, nothing fancy (as far as I can tell)

For this filter, the average age chart shows a monthly average for January to be 20 days  

So far so good.

However, when I tried to be more granular to see how the different types of the tickets age, this is where things are not adding up.

So, keep in mind that for ALL ticket in the filter above, the average is 20 days. Once I add another filter example:

Project="Service Desk" and created \>= -52w AND Resolved \>= -52w AND assignee in ("service desk group") AND Module=SOMETHING

the average age jumps to 30, 40 or 70 depending on the selected module.

I went through all MODULE groups as well as MODULE NOT IN (everything else selected) and all totals were significantly higher than 20 days.  
I would have thought the law of averages means that some will be more than 20 and some less, but that's not the case.

Can anyone shed some light on this?


Answers:
author: Danut M _StonikByte_
body: Hi [@George Abdo](/t5/user/viewprofilepage/user-id/5303873),

Perhaps one of the module has some issues with a much higher age. And taken in the context of a module where are less issues than in your global filter, this increases the average.

Be aware that there are alternatives to this gadget. Take a look over this article: <https://community.atlassian.com/t5/App-Central/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369>.

The Cycle Time Trend, Histogram, Control Chart or WIP Agin Chart gadgets offered by our [Great Gadgets](https://marketplace.atlassian.com/search?query=stonikbyte%20great%20gadgets%20agile%20) app are good options for determining the (average) age. You could try these and see if they show the same average or not.

Hope this helps.

Danut.

comments: author: George Abdo
body: Thanks [@Danut M _StonikByte_](/t5/user/viewprofilepage/user-id/502420)   

I'll give them a try when I get a chance.

Still, an average of individual subgroup averages should equal to the average of the whole!


author: Danut M _StonikByte_
body: Hi [@George Abdo](/t5/user/viewprofilepage/user-id/5303873),

If in the whole you have these values:

10, 1, 1, 1, 2 the average will be 15 / 3 = 5

But if in a group you have:

10, 2 =\> average is 12/2 = 6

Danut.


author: George Abdo
body: You are right in your calculations.

I revisited my old maths lessons from many years ago, and I realised my mistake.

The average of averages is not the same as the average of the whole unless all values are equal, which explains the discrepancies I am seeing.


author: Emre Toptanc? _OBSS_
body: Hello [@George Abdo](/t5/user/viewprofilepage/user-id/5303873)

Jira's own Issue Age and Resolution Time charts/gadgets offer limited flexibility and details. For maximum flexibility and details, I suggest you use a marketplace app for this. Even if you don't plan to purchase the app, you can use it to cross-check its results with Jira's own charts.

Our team at OBSS built [Time in Status](https://marketplace.atlassian.com/apps/1211756/) exactly for this. 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** or each **assignee**.

![tisCloud_StatusDuration_LeadTime_with Estimates.png](https://community.atlassian.com/t5/image/serverpage/image-id/170015i6CBCFEFDC1640B76/image-dimensions/215x97?v=v2 "tisCloud_StatusDuration_LeadTime_with Estimates.png") ![tisCloud_AssigneeDuration.png](https://community.atlassian.com/t5/image/serverpage/image-id/246449iA6FF27980A832D08/image-dimensions/199x96?v=v2 "tisCloud_AssigneeDuration.png")

You can combine the time for multiple statuses to get metrics like **Issue Age, Cycle Time, Lead Time, Resolution Time** etc.

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*or average resolution time per sprint, week, month, issuetype, request type, etc. Grouping 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](https://community.atlassian.com/t5/image/serverpage/image-id/170014i3A4C82B8C3EE58D2/image-dimensions/235x72?v=v2 "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 for Jira Cloud.

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.

![Gadget_AverageStatusDurationByComponent.png](https://community.atlassian.com/t5/image/serverpage/image-id/170017i541738A81A7EBA80/image-dimensions/165x135?v=v2 "Gadget_AverageStatusDurationByComponent.png") ![tisCloud_StatusDuration_LeadTime_Chart.png](https://community.atlassian.com/t5/image/serverpage/image-id/170018i88B62F9CBD7B6C6E/image-dimensions/198x94?v=v2 "tisCloud_StatusDuration_LeadTime_Chart.png") ![tisCloud_IssueView_Data.png](https://community.atlassian.com/t5/image/serverpage/image-id/272943iB7FF085E8C1AE97A/image-dimensions/186x101?v=v2 "tisCloud_IssueView_Data.png")

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

EmreT


Tags: chart

cloud

dashboard

jira-service-management

jira-service-management-cloud