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; } } }

Please confirm - Status duration requires paying for an add-on

unknown

I've had several managers come to me asking for reports on how long an issue remains in any given status. Based on my research, this request has been floating around since 2012.

Is it true that I have to buy an add-on to achieve a simple how long query? The only other thing I can think of is to capture a system date during a status transition and store it for comparisons.

P.S. Paying an additional subscription fee for functionality that should be in the base product likely won't be approved.

Accepted answers

Jack Nolddor [Sweet Bananas]

Hi Robin C.

Have a look to Jira Charting Plugin a FREE app developed by Atlassian team itself
Will offer some handul gadget relating status duration.

Regards

All comments

Jack Nolddor [Sweet Bananas]

Hi Robin C.

Have a look to Jira Charting Plugin a FREE app developed by Atlassian team itself
Will offer some handul gadget relating status duration.

Regards

unknown

Thank you, Jack. I appreciate it! I didn't see it when I was reviewing the add-ons.

I was all excited until I read that it wasn't compatible with JIRA 8.2. We just upgraded recently or I would be all over it.

Jack Nolddor [Sweet Bananas]

I believe that comment is outdated since the app is compatible with latest Jira version as shown here:

unknown

Bless you for noticing what I didn't! I'm going to give it a try.

Happy dance.jpg

unknown

Although I was very excited about the plug in, it is not showing the results I expected.

I finally found additional documentation (not included in the download) that states "This gadget will only show the average time spent on the selected statuses for issues that are resolved with a resolution set on the same day. For example, there are 10 issues resolved on March 16, the total time spent on each selected status will be divided by 10 issues, despite when these issues are created."

Since my managers want to see the status duration for both open and closed tickets, it looks like I'm back to the drawing board and will have to try to capture a date during a status transition and store it for evaluation during reporting.

Rashawn Johnson

Confirm

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server