nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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?

Accepted answers

Kris G _Alacriz_

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

All comments

Kris G _Alacriz_

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

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software