Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-17680

On burndown reports, display issues on correct sprint even if they were completed once the sprint was closed



    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      Problem Definition

      The Release Burndown report return completed issues on the incorrect Sprint if the issues were finished during a Sprint they are not added too.
      The same applies to Epic Burndown report

      Also, The Release Burndown will show the issue under the latest started sprint by the time the issue was completed.

      Steps to Reproduce

      1. Create a release (ABC) and two Sprints (123 and 789)
      2. Create a new issue TEST-123 and add it to the Sprint 123 in the release ABC
      3. Start the Sprint 123
      4. Finish the Sprint 123 and move the open issue to the Backlog or don't fill resolution field
      5. Start the sprint 789 with different issues (Don't add the Issue TEST-123)
      6. Close the issue TEST-123 (Adding its resolution)
      7. Complete the Sprint 789
      8. Navigate to the Release BurnDown Report and select the release ABC

      Suggested Solution

      There should be a note mentioning the issue was not part of the sprint.
      Or the correct sprint should be listed and a note informing the issue was completed after the sprint.


        Issue Links



              Unassigned Unassigned
              psilveira Paula Silveira
              1 Vote for this issue
              2 Start watching this issue