Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
3
-
Severity 3 - Minor
-
Description
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
- Add ticket A to Sprint A but don't start Sprint A.
- Move ticket from Sprint A to Sprint B do not start Sprint B.
- Add a fix version to Ticket A.
- Start Sprint A (note that the ticket A is already moved out of Sprint A).
- Move the ticket to Done.
- 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
Attachments
Issue Links
- relates to
-
JSWCLOUD-25260 Sprint Report includes story points estimated after the story was removed from sprint
- Gathering Impact