-
Bug
-
Resolution: Unresolved
-
Medium (View bug fix roadmap)
-
None
-
None
-
17
-
Severity 2 - Major
-
2
-
Summary
Using recursive transitions (from a given to status to itself) impact negatively Agile reports such as:
- the Control Chart
- the Cumulative flow diagram
Impact on the Control Chart
The Jira Control Chart doesn't handle recursive transitions (from a given to status to itself) correctly. It will only count the time spent in the first "cycle" on that status.
Steps to Reproduce
- Create a Scrum Project;
- Create a Sprint;
- Create an issue and put in in the Sprint then start the Sprint;
- Transition the issue from "To Do" to "In Progress";
- From "In Progress", wait a couple of minutes and then execute the transition to "In Progress";
- Wait another couple of minutes and execute the transition to "Done";
- Go to the board > Reports > Select Control Chart > Select All Columns
- Click on the issue on the chart and it will only show the cycle time for the first cycle in the "In Progress" status. For example:
- To Do = 3m
- In Progress = 2m
- Cycle Time = 5m
Using Jira Suite Utilities, you can see the time for the second cycle in the "Transitions" panel.
Expected Results
The report should sum up "Cycle Time" for the two cycles in that status, or for as many cycles that might happen.
Actual Results
Cycle Time is only calculated for the first (edit: last) cycle in the status.
Notes
This is actually an expected behavior according to the Control Chart documentation:
[...]
Tip 3: Exclude current work
The Control Chart shows data for issues that have been in a selected column but are no longer in a selected column. This gives the cycle time (total elapsed time) for the issues. However, by default this will include issues which are still moving across the board.
[...]
Impact on the Cumulative Flow Diagram
The Cumulative Flow Diagram might show negative values, when using the Refine button to select a specific status.
Workaround
Do not transition issues to the same status.
- duplicates
-
-
- Closed
-
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
![[Atlassian Documentation] Page](https://confluence.atlassian.com/images/icons/favicon.png "[Atlassian Documentation] Page"){kind=icon}
- was cloned as
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-12122] Using recursive transitions impact negatively Agile reports (Control Chart, Cumulative flow diagram)
We just found about this bug and as a consequence, since such transitions are possible - even if by mistake, we can't use the control chart anymore...
I would suggest you either fix this problem, or not allow to transition from a status to itself. Not doing any of these fixes - just disqualifies one of the better reports Jira has.
Dear Atlassian,
This issue celebrated a 5-year anniversary this month with no movement so far.
Just wanted to add a comment that it has a big impact on our work as well and it would be nice to see someone having a look at it.
Thanks.
Hi Atlassian.
For this reason, in our context, unfortunately Control Chart is a feature that proves to be unusable.
Is it by any chance possible to push this bug correction and is it possible to know the plans when it is going to be done. Our development teams are very dependent on this functionality to work and if the plan is far into the future we will have to start looking for workarounds.
Thanks.
Madura Rodrigo
added a comment - Same status transition is very usefull and this is a huge bug in control chart which cause to mislead all statistics, if we used loop transitions , any plan from Attlassian to fix this?
Adrian Stephen can you increase the priority of this?
Madura Rodrigo
added a comment - Same status transition is very usefull and this is a huge bug in control chart which cause to mislead all statistics, if we used loop transitions , any plan from Attlassian to fix this?
Adrian Stephen can you increase the priority of this? 
Deleted Account (Inactive)
added a comment - Dear JIRA team, I stumbled across this bug as well. Can you tell me when it will be fixed?
Thanks!
Alex
Deleted Account (Inactive)
added a comment - Dear JIRA team, I stumbled across this bug as well. Can you tell me when it will be fixed?
Thanks!
Alex Hello, voting +1 for this issue. We are using loop transitions massively (because this is quite comfortable for users), but Control chart seems not to be usable in this case.
Bryan Rowe
added a comment - This is a huge bug when teams have columns such as 'blocked'. Hi Atlassian.
Is it by any chance possible to push this bug correction and is it possible to know the plans when it is going to be done. Our development teams are very dependent on this functionality to work and if the plan is far into the future we will have to start looking for workarounds. Though I do not think there is any simple workaround.
Thanks.
This was reported by our development teams. As it is possible to create transitions looping back to the same step, it is natural that the time in that status should be summarized. Making loops like this can be very useful when for instance making approvals that can be done in parallel. So the workaround to have a dummy status I cannot see as acceptable neither do I think the note of the expected behavior of the Control chart is correct.
This affects all our Development teams so we are heavily dependent on this functionality, so please prioritize the correction of this bug.
I've seen this actually only count the cycle time from the last period in a column, not the first.
Example 1 - A ticket is In-Progress for a couple of weeks, the team member accidentally moves it to In-Progress again (because workflow is relaxed with All transitions to all statuses), and then transitions it forward (to Done or whatever the next column/status is) and the In-Progress time is represented as only 1m in the Control Chart!
Example 2 - A ticket needs to move back to In-Progress after it has spent time elsewhere. After it moves forward, the Control Chart appears to only take the latest time spent in In-Progress.
This negatively impacts averages and mis-represents cycle times.