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

Issues removed from active sprint are no longer shown in the Sprint Report or Burndown Chart

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • None
    • Archived Jira Software Cloud
    • None

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Summary

      Issues removed from an active sprint (either into a next planned sprint or backlog) do not appear under "Issues Removed from Sprint" in the Sprint Report and the Burndown Chart does not show Scope Change

      Environment

      • JIRA v1000.35.2

      Steps to Reproduce

      1. Create a Sprint in a JIRA Software Project
      2. Add Issues to the Sprint
      3. Start Sprint
      4. Move issues from the Active Sprint into either another Planned Sprint or the Backlog
      5. View Sprint Report or Burndown Chart

      This is seen in instances with Parallel Sprints both enabled and disabled

      Expected Results

      Both the Sprint Report and Burndown Chart should show Scope Change where these issues are being removed.

      Actual Results

      No errors in the logs

      Notes

      If the Moved Issues are re-added, the Burndown Chart shows scope change; the Sprint Report shows the Issues as Incomplete.

      Workaround

      none

        1. 1.IssuesInSprint.png
          1.IssuesInSprint.png
          71 kB
        2. 2.SprintReport.png
          2.SprintReport.png
          76 kB
        3. 3.MovedIssue.png
          3.MovedIssue.png
          74 kB
        4. 3.SprintReport2.png
          3.SprintReport2.png
          69 kB
        5. 4.Burndown.png
          4.Burndown.png
          80 kB
        6. 5.ReAddIssues.png
          5.ReAddIssues.png
          114 kB

              hsu@atlassian.com Henry Su
              scranford Shawn C
              Votes:
              10 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: