Basically, customer mention about the accuracy of Average Age Chart Gadget is affected when there is a user reopen a very old dated issue to modify the resolution as the chart will always take in issues with any latest resolution date changes.

Customer Feedback:

lately a question occured about the behaviour of the average age chart gadget. A colleague uses this chart to monitor the age of issues in some projects that we use for support. This week he looked at the chart and all the bars in the average age chart had risen from about 10 to 14 days to more then 100 days.
After a short investigation I found that he had previously reopened a 2-year old issue in order to change the resolution. So the issue also got a new resolution date. The new resolution date of that issue caused the average age gadget to "think" the issue has been unresolved before and therefore included the issue in the calculation of the average age for the past days, weeks and months. I think this behaviour is not right and distorts the data shown in the average age chart.
The issue was already resolved for a long time. Reopening it and setting a new resolution made it appear that it was unresolved all the time, although it was closed, just with another resolution. For us it would be better if the average chart would only take the first resolution date into account.
How could we handle issues that need to be reopened without distorting the average age chart? Is it possible to change the resolution without changing the resolution date?

Support Feedback

Perhaps there could be some additional settings to be implemented to set issues that have been more than 30 days should not count into the Average Age Chart.