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

The burndown chart is not showing the information when an issue is removed from the sprint.

XMLWordPrintable

      Summary

      The burndown chart is not showing the information when an issue is removed from the sprint.

      Steps to Reproduce

      1. create sprint A
      2. put issue 1 in sprint A
      3. start and close sprint A without completing issue 1
      4. create sprint B
      5. put issue 1 and 2 in sprint B
      6. start sprint B
      7. remove both issues from sprint B

      Expected Results

      Burndown chart shows both issue 1 and issue 2 as being removed from sprint B

      Actual Results

      Burndown chart only shows issue 2 as being removed from sprint B

      Notes

      • This is affecting issues that don't have an estimation.
      • Seems to be only affecting Original Time Estimate & Original Story Points estimation only.
      • Issue Type such as Task is not affected.

      Workaround

      • Workaround 1 (Original Story Points)
        The only known workaround for now is to put the issue back in the Sprint after removal and then remove again
      • Workaround 2 (Original Time Estimate)
        Assign 0m to the issue's estimation will keep it in the report.

          Form Name

            [JSWSERVER-15541] The burndown chart is not showing the information when an issue is removed from the sprint.

            set-jac-bot made changes -
            Fixed in Enterprise Release/s New: [Download 8.5|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html]
            Ignat (Inactive) made changes -
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Stanislav Natkovskyi (Inactive) made changes -
            Fix Version/s New: 8.9.0 [ 91513 ]
            Fix Version/s New: 8.8.1 [ 91514 ]
            Stanislav Natkovskyi (Inactive) made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Stanislav Natkovskyi (Inactive) made changes -
            Assignee New: Stanislav Natkovskyi [ snatkovskyi ]
            Stanislav Natkovskyi (Inactive) made changes -
            Fix Version/s New: 8.5.5 [ 91600 ]
            Stanislav Natkovskyi (Inactive) made changes -
            Link New: This issue is duplicated by JSWSERVER-18147 [ JSWSERVER-18147 ]
            Stanislav Natkovskyi (Inactive) made changes -
            Remote Link New: This issue links to "Code Health › Unit Tests code coverage - Jira Software › stable-issue-8.5-JSWSERVER-15541-handle-multiples-sprints (server-gdn-bamboo)" [ 475771 ]
            SET Analytics Bot made changes -
            UIS Original: 6 New: 5
            SET Analytics Bot made changes -
            UIS Original: 11 New: 6

              snatkovskyi Stanislav Natkovskyi (Inactive)
              rtandon@atlassian.com Ruchi Tandon
              Affected customers:
              68 This affects my team
              Watchers:
              51 Start watching this issue

                Created:
                Updated:
                Resolved: