Measure Rework by transition status

Question

we are using a standard workflow for a Scrum Board of:

* To Do
* Blocked
* In Progress
* Review
* Feature Test
* Done

Where "done" is that the story is ready for wider Systems Test. I would like to monitor / measure how often a story / task fails feature test and is transitioned back to "In progress" or "blocked".

We have Transition History using JMWE within story, but I would like to measure quality but reporting on total re-work for a team, a project, a sprint or an individual story.

Thanks

Dan

Mehmet A _Bloompeak_ · Accepted Answer

Hi @dan.laasnareuter ,

You can try Status Time app. It provides reports on how much time passed in each status as well as status entry dates and status transition count.

Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project). And all these are available as gadgets on the dashboard.

Here is the online demo link, you can see it in action and try.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.

Please note that I'm one of the members of the Bloompeak team.

Emre Toptancı [OBSS] · Accepted Answer

Hello @dan.laasnareuter ,

If you are interested in a ready built solution, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status has reports that show you how many times each status or each transition was used for each issue (It also allows you to see how much time each issue spent on each status or assigned to each assignee.)

You can calculate averages and sums of report values grouped by issue fields you select. (For example see the average reopen count per issuetype or average resolution time per project and assignee.)

The app calculates its reports using already existing Jira issue histories so when you install the app, you can get reports on your past issues as well. You don't need to modify your workflows.

Using Time in Status you can:

* See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
* See status and transition use counts.
* Calculate averages and sums of those values grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
* Export your data as XLS, XLSX or CSV.
* Access data via REST API.
* See Time in Status data and charts on issue view screen and Jira dashboards.

Timepiece - Time in Status for Jira

EmreT

Mariana_Pryshliak_Saasjet_qysy8m · Accepted Answer

Hello @dan.laasnareuter

As an alternative, you can try the add-on developed by my SaaSJet team - Time in Status for Jira Cloud.

This add-on measures time spent in each status. It also has the Status Entrance Date report, which shows the date and time when every issue has entered each of the statuses for the first time.

And Status Count report, which calculates how many times an issue has been in each status. So you can track each issues' movements and how many times it has occurred.

If you need to get data not only a particular Assignee but the whole project, just choose necessary filtering: by Assignee or by Project)

I hope you find it helpful

Best regards, Mariana