Counting The Total Number of in-progress time

[renzo.aguila]

Hello,

I would like to ask if it is possible in JIRA to have the total efforts of bugs in "In-progress" status.

Like for example, A bug is filed to the developer. Then it is now in set as "in progress".  And then, It was set again to done and is assigned in QA.  But it just so happened that the issue still exist.  It will now be assigned to the developer again and will set the status to in-progress again.

Hoping for your quick response.

[Petter Gonçalves]

Hello Renzo,

Answering your questions:

1 - There are some reports on the add-on that are based on the worklog field, however, the Time in Status report is not based in any field and provide the entire time that an issue was on a determined status.

2 - I performed a test and I confirm that the Time in Status report sum the entire time that an issue was in a determined status, not mattering the assignee or status changes.

That been said, if you move your issue to another status and then move it back to the original, the report will keep counting the time for where it was before the status change.

E.g: I created a new issue and left it in the status Open for 0.59h, and then I moved it to In Progress. After 0.01h, I moved it back to Open and left it for more 0.16h. Now, the report is displaying the issue in the Open for 0.75h and In Progress for 0.01h:

[Petter Gonçalves]

Hello Renzo,

you can check the documentation below to use the Average time in status Gadget:

https://community.atlassian.com/t5/Jira-questions/How-do-I-get-the-quot-Average-Time-In-Status-quot-chart-to-work/qaq-p/227721

Also, there is a plugin that provides this functionality in more formats:

- Time Reports

[renzo.aguila]

Hello @Petter Gonçalves,

I was checking the proposed solutions to this problem and seeing time report plugin is the most convenient way to see those time exhausted by user on an issue.

However, my questions are the following:

1. Does time report only check those time logged in the timesheet regarding on what issue was worked on?

2. If no is the answer, Is time reports capable of computing all the turnaround time even if the issue/defect keeps bouncing back to the originator and the next assignee?

Sorry for the questions, I just am confused with what the time reports can do despite of the documentation