Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
8.20.11, 9.4.0, 9.4.14, 9.4.15
-
None
-
8.2
-
2
-
Severity 3 - Minor
-
Description
Issue Summary
Story Point value reset to zero/removed is ignored in Burnup Chart Work scope.
Steps to Reproduce
Scenario 1
- Create a sprint with a few issues
- Add Estimates to issues
- Start the sprint
- Now, increase/decrease the estimate points to any issues and the same will reflect in the Burnup chart
- For any issue in a sprint, try to reset the estimated value to zero or remove the estimated value then, Burnup chart ignores to update work scope details.
Burnup chart should show the value as reduced from 15–>10 but, when zero/remove estimated value Burnup chart ignores to update work space details.
Scenario 2
- Create a new Story issue (TEST-1) and assign 3 story points.
- Create a second Story issue (TEST-2) and assign 3 story points.
- Remove all the story points from TEST-1 (story points estimation should be null or empty).
- Move TEST-2 to a new sprint and start the sprint.
- Assign TEST-1 to the active sprint.
- Move TEST-1 and TEST-2 to DONE status.
- Closed the active sprints.
- In the burnup chart, we can see TEST-1 completed works were calculated as 3 and included in the completed work and work scope:
Expected Results
Burnup chart should show the Work scope value changing to '0'.
Actual Results
Burnup chart ignores when we reset the estimated value to Zero/removed.
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-18127 The Burnup chart doesn't consider estimation changes when the Story points estimation is set to 0 or none
- Gathering Impact
-
JSWCLOUD-21602 burnup and burndown charts take the last known value for story points, if that field is set to 0 or cleared
- Long Term Backlog