-
Bug
-
Resolution: Fixed
-
Low
-
7.3.0, 7.2.2, 7.7.0, 7.11.2
-
None
-
7.02
-
16
-
Severity 3 - Minor
-
5
-
Summary
The burndown chart is not showing the information when an issue is removed from the sprint.
Steps to Reproduce
- create sprint A
- put issue 1 in sprint A
- start and close sprint A without completing issue 1
- create sprint B
- put issue 1 and 2 in sprint B
- start sprint B
- remove both issues from sprint B
Expected Results
Burndown chart shows both issue 1 and issue 2 as being removed from sprint B
Actual Results
Burndown chart only shows issue 2 as being removed from sprint B
Notes
- This is affecting issues that don't have an estimation.
- Seems to be only affecting Original Time Estimate & Original Story Points estimation only.
- Issue Type such as Task is not affected.
Workaround
- Workaround 1 (Original Story Points)
The only known workaround for now is to put the issue back in the Sprint after removal and then remove again - Workaround 2 (Original Time Estimate)
Assign 0m to the issue's estimation will keep it in the report.
- is duplicated by
-
JSWSERVER-18147 Issue removed from the Sprint does not appear in the Sprint report under Issue removed from Sprint
- Closed
- relates to
-
JSWSERVER-14984 Issue removed from Sprint not showing in Burndown Chart or Sprint Report
- Closed
-
JSWSERVER-13810 Issues removed from active sprint are no longer shown in the Sprint Report or Burndown Chart
- Closed
-
JSWSERVER-15747 Issues removed from sprint not showing up in Agile Reports after upgrade
- Gathering Impact
- mentioned in
-
Page Loading...