Jira gadget average age

[Michael Strickler]

Hello everyone

We are working with Jira and the gadget "Average age issue".

The gadget counts with the data fields "created" and "updated".

If we open an issue and fix them in one week "resolved them" and then we update the issue later, it will counts the time between "created" and "updated". However, for us, this is very uninterested; we will know how long the bug fixing process for a developer takes.

So the time between "created" and "resolved"!

Have you any idea how we can work whit Jira and the gadget "Average age issue" in this way?

[Kris G _Alacriz_ · Accepted solution]

Hello @Michael Strickler-

No matter what base query you are using for the Average Age Chart gadget, it always calculates age based on the duration for which an issue is NOT resolved or closed.

To overcome this, you need to resolve issues, wherever applicable, before you try to analyze the gadget. As you may be aware if an issue is updated, it's an issue in progress for Jira. 

If this explanation does not help, please let me know the status and resolution at each stage of the issue that gives you unwanted results. 

best,
Kris G

[Michael Strickler]

no text

[Michael Strickler]

Hello Kirs

Thank you for answering me.

I will do an example:
If a customer reports an error, then the developer opens a new issue. If he sets out today (June 27, 2018) to fix the error (for example, an incorrect calculation is made in a function) and he fixed it on June 31, 2018 and set the issue to resolved. The developer worked on it for 4 days.

On August 3, 2018, the developer notices that one more detail is missing. He reopens the issue and corrects a value in the issue. He does not work on the program code, he just writes a missing documentation (as an example a wrong release number). Then the issue is closed again.

According to the gadget (average age issue), the age of the issue is 7 days. As it measures the duration between created and updated.
But this is not the information we need. We need the time when the developer actually did code work, not when he corrected a documentation error.

Is there any way this gadget measures the duration between created and resolved? Or is there a way that we can configure it differently? At the moment we only need the duration in days, no else more.
Or is there another gadget on the marketplace that lets us measure the age of an issue the way we like,to use the age for the average age of all issues in a project?
Or what else can we do to solve this problem?

Thank for your answer.

Best regards
Michael

[Michael Strickler]

Please let me mention an addition. We do not need a time tracker that measures working time in detail or many different time measurements or reports. We only need one look back today for a definite time.

[Kris G _Alacriz_]

Hi @Michael Strickler-

What makes you think that the Average Age gadget also takes the extra 3 days to calculate the age of the issue ? As per the definition by Atlassian, an issue is defined as unresolved if it has no value in the system Resolution field. But since this issue was already closed earlier, I am assuming that it will have the Resolution field already set and hence should not take the 3 days into account. Please refer to this link for the definition of the Average Age Gadget https://confluence.atlassian.com/jira064/adding-the-average-age-gadget-720417014.html

In either case, the issue you are facing should be resolved by another Gadget named Resolution Time Gadget. More details are in its description page on Atlassian site.  

Please let me know if that helps. 

best,
Kris G 

[Archana Devi]

Hi,

This post is exactly same as my requirement. I would like to display the total time taken to resolve my issue in the means of code change. This is nothing but the time taken between "created" time and "resolved" time (Not the closed/updated time).

I am aware that there are a couple of gadgets which are useful to display the Average age for open issues and Resolution time for resolved issues.

Both of the gadgets are displaying the Total No. of days according to each month. But my requirement is, I want to know the total time taken to resolve my issue as per my Release version column.

For example, I got 10 issues logged post to my 1st release (5.1). Those issues may have logged in different dates and resolved in different dates. But the issues were caused post to that particular release, so users will raise the Bug with reference to the Release number.

So I just want to display the Release version, No.of Bugs logged for that version and their corresponding Resolution time which is nothing but Turnaround Time.

Could anyone please help me to achieve this

Also I am very much keen to know any other possible ways to display the results as per the requirements. Please provide me suggestions to achieve this.

[Jacek Zarzycki]

Please take into account that when we combine tasks with each other, the update date also changes.
So if I link the new task A with the old B, for example, two years old, then task B is counted and distorts the statistics.
We did not work on it at all, We only created the link between B and A tasks.

Is it not possible to add a list to the configuration where the administrator can choose whether to use the default value or "Resolved Date"?

[Michael Strickler]

No text.