Release Burndown: Sprint includes story points after an issue was removed from it (before starts) and completed in a different Sprint (after starts)

XMLWordPrintable

    • 3
    • Severity 3 - Minor

      Issue Summary

      Currently, if you remove a estimated story from a sprint (Sprint A) before it starts, and later you move to "Done" that story in other sprint (Sprint B), in the Release Burndown report the original sprint (Sprint A) will include the story points of the removed and completed story.

      Steps to Reproduce

      1. Add ticket A to Sprint A but don't start Sprint A.
      2. Move ticket from Sprint A to Sprint B do not start Sprint B.
      3. Add a fix version to Ticket A.
      4. Start Sprint A (note that the ticket A is already moved out of Sprint A).
      5. Move the ticket to Done.
      6. Check the reports.

      Expected Results

      The Story Points value displayed in the Release Burndown for Sprint A, should not include story points from issues that were removed (before the Sprint A starts) and completed in a different Sprint (after Sprint A starts). 

      Actual Results

      The Story Points value displayed in the Release Burndown for Sprint A, are including the Story Points from issues that were removed (before the Sprint A starts) and completed (after the Sprint A starts) in a different sprint.

      Workaround

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

            Assignee:
            Unassigned
            Reporter:
            Jairo Ortiz
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: