Control Chart - Really Long (Incorrect) Time in Status

Question

Hey friends, I've got a puzzler that I've been presented with by a couple of co-workers. What we're seeing is that a few issues are reporting extremely long times in a particular status in the Control Chart. I've found a couple of commonalities:

1. Both issues bounced back and forth between "In Development" and "Ready for QA Testing" and in one of those transitions there is no "time in source status" present in the "Transitions" tab.

2. Both issues were changed from Tasks to Stories days prior to this happening. Maybe unrelated but I thought I would put it out there.

In both cases the "QA/Deploy" status in the Control Chart is showing a huge (incorrect) number.

Any thoughts?

Mehmet A _Bloompeak_ · Answer

Hi @Doug Pflueger ,

As an alternative you can try Status Time Jira app developed by our team.  It has 1-month trial period, at least you can install it and compare the report with the control chart. It will help you to find out the problem with the control chart.

The app provides reports on how much time passed in each status. By grouping statuses you can get resolution time(E.g from new status to done status). You can also export the report as CSV.

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 by any field(eg. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too. Here is the online demo link, you can see it in action and try without installing the app.

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

Emre Toptancı [OBSS] · Answer

Hello @Doug Pflueger

I believe changing the issue type from Task to Story should not have such an effect. The missing information in the Transitions tab seems to be more relevant. The prime suspect here is incomplete/inaccurate issue history.

I suggest you check the History tab of those issues to see if there are any missing changes, especially status changes. In the History tab, you should be able to see all status changes of the issue. I mean it should be showing the date when the issue was created when it was transitioned from A to B, from B to C, from C back to B, and so forth. Up to the current status of the issue. There shouldn't be any missing status changes in the issue history.

Our team at OBSS built Timepiece - Time in Status for Jira app for very similar needs. It provides more reports that are more detailed and flexible than Control Chart. Checking the reports calculated by Time in Status might help you identify the cause. Installing the app even as a trial can help.

Time in Status allows you to see how much time each issue spent on each status. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time, or Lead Time.

You can calculate averages and sums of those durations grouped by the issue fields you select.

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

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

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.
* Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
* Export your data as XLS, XLSX, or CSV.
* Access data via REST API. (for integrations)
* Visualize data with various chart types.
* See Time in Status reports on Jira Dashboard gadgets

Timepiece - Time in Status for Jira

EmreT

.