Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-12122

Using recursive transitions impact negatively Agile reports (Control Chart, Cumulative flow diagram)

XMLWordPrintable

      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

      1. Create a Scrum Project;
      2. Create a Sprint;
      3. Create an issue and put in in the Sprint then start the Sprint;
      4. Transition the issue from "To Do" to "In Progress";
      5. From "In Progress", wait a couple of minutes and then execute the transition to "In Progress";
      6. Wait another couple of minutes and execute the transition to "Done";
      7. Go to the board > Reports > Select Control Chart > Select All Columns
      8. 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.

        1. loop.png
          loop.png
          28 kB
        2. loop1.png
          loop1.png
          14 kB
        3. loop2.png
          loop2.png
          36 kB

              Unassigned Unassigned
              astephen@atlassian.com Adrian Stephen
              Votes:
              37 Vote for this issue
              Watchers:
              40 Start watching this issue

                Created:
                Updated: