Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
2
-
Severity 3 - Minor
-
Description
Issue Summary
Currently, if you remove a non-estimated story from a sprint before it starts, and later you estimates that story while in the other sprint, the sprint report of the original sprint will include the newly estimated story points for the issue removed from the sprint.
Steps to Reproduce
- Create Story A on Sprint A. Start Sprint A
- Move Story A to Sprint B before closing Sprint A. Close Sprint A
- Estimate Story A on Sprint B
- Generate Sprint Report from Sprint A.
Expected Results
Story A should appear as "Issues Removed from Sprint" but do not show any estimation or scope change, as no estimation was done to this story while in the Sprint A.
Actual Results
Story A appears with a scope change in it's story points estimation in the Sprint Report of Sprint A, even though it was only estimated when it was assigned to Sprint B.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
Attachments
Issue Links
- is related to
-
JSWCLOUD-25350 Release Burndown: Sprint includes story points after an issue was removed from it (before starts) and completed in a different Sprint (after starts)
- Gathering Impact
- mentioned in
-
Page Loading...