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

      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

        1. Screen Shot 2021-02-12 at 15.41.24.png
          Screen Shot 2021-02-12 at 15.41.24.png
          276 kB
        2. Screen Shot 2021-02-12 at 15.42.13.png
          Screen Shot 2021-02-12 at 15.42.13.png
          290 kB
        3. Screen Shot 2021-02-12 at 15.42.46.png
          Screen Shot 2021-02-12 at 15.42.46.png
          277 kB
        4. Screen Shot 2021-02-12 at 15.43.09.png
          Screen Shot 2021-02-12 at 15.43.09.png
          359 kB
        5. Screen Shot 2021-02-12 at 15.43.35.png
          Screen Shot 2021-02-12 at 15.43.35.png
          309 kB
        6. Screen Shot 2021-02-12 at 15.44.02.png
          Screen Shot 2021-02-12 at 15.44.02.png
          326 kB
        7. Screen Shot 2021-02-12 at 15.55.09.png
          Screen Shot 2021-02-12 at 15.55.09.png
          235 kB
        8. Screen Shot 2021-02-12 at 15.55.23.png
          Screen Shot 2021-02-12 at 15.55.23.png
          314 kB
        9. Screen Shot 2021-02-12 at 15.55.52.png
          Screen Shot 2021-02-12 at 15.55.52.png
          197 kB
        10. Screen Shot 2021-02-12 at 15.56.06.png
          Screen Shot 2021-02-12 at 15.56.06.png
          286 kB
        11. Screen Shot 2021-02-12 at 15.59.24.png
          Screen Shot 2021-02-12 at 15.59.24.png
          192 kB
        12. Screen Shot 2021-02-12 at 15.59.37.png
          Screen Shot 2021-02-12 at 15.59.37.png
          300 kB
        13. Screen Shot 2021-02-12 at 15.59.59.png
          Screen Shot 2021-02-12 at 15.59.59.png
          305 kB
        14. Screen Shot 2021-02-12 at 16.01.52.png
          Screen Shot 2021-02-12 at 16.01.52.png
          377 kB
        15. Screen Shot 2021-02-12 at 16.02.13.png
          Screen Shot 2021-02-12 at 16.02.13.png
          304 kB
        16. Screen Shot 2021-02-12 at 16.02.31.png
          Screen Shot 2021-02-12 at 16.02.31.png
          272 kB

            [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

            There are no comments yet on this issue.

              Unassigned Unassigned
              imurakami@atlassian.com Murakami
              Affected customers:
              2 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated: