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

Scope Change caused by moving issue to another sprint is only presented at the first time on the Burndown Chart and Sprint Report

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 8.13.1
    • Reports

      Issue Summary

      When the same issue has the sprint changed from Sprint A, then to Sprint B, and later on, to Sprint C, Sprint A shows the scope change but Sprint B does not show the issue and the scope change at the Burndown Chart and the Sprint Report.

      Steps to Reproduce

      1. Enable "Parallel Sprints" at the Admin > Applications > Jira Software Configuration
      2. Create some stories a, b, c, d with 1 point each
      3. Create sprint 1
      4. Add stories a e b to the sprint 1
      5. Start sprint 1 (it will have 2 points to be done from the story a and story b)
      6. Transition story a to done (remaining 1 point to be done from story b)
      7. Create sprint 2
      8. Edit story b and change the sprint to sprint 2, confirming the scope change
      9. move story c from the backlog to sprint 2
      10. Complete sprint 1 (1 point done, 1 point removed)
      11. Start sprint 2 (2 points to be done from story b and story c)
      12. Create sprint 3
      13. Transition story c to done (1 point)
      14. Move story d from backlog to sprint 3
      15. Edit story b and change the sprint to sprint 3, confirming the scope change

      Expected Results

      Burndown Chart/Sprint Report for Sprint 2 was expected to be equal to the Burndown Chart /Sprint Report for Sprint 1

      • Starting with 2 points, changing to 1 point;
      • Scope change caused by story b

      Actual Results

      For Sprint 2, Both Burndown report and Sprint Report do not show story b
      The starting value, initially showing 2 points, is now starting at 1 point.
      The scope change is not presented.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              imurakami@atlassian.com Murakami
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: