Description
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
When viewing the Release Burndown chart, if an issue has the fixVersion value updated, the report shows it as an unestimated issue. It follows below the steps to reproduce this behaviour:
1 - create a Scrum project and add a version (V1 for example)
2 - create some stories, set an Original Estimate and set fixVersion to V1
3 - create a sprint and add the stories created on step 2 to this sprint
4 - go to the Release Burndown report. It will show the total estimate and “0% of unestimated issues” message, just like in release_burndown_original.png
5 - open one of the stories and remove V1 from the fixVersion field
6 - go back to Release Burndown report. It will show “X% of issues do not have an estimate (1 of Y)”, just like in release_burndown_updated.png
Attachments
Issue Links
- duplicates
-
JSWSERVER-11382 Release burndown chart includes issues that were not completed, but got removed from the version, in the unestimated issues statistics as unestimated issues, even if they are estimated
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- was cloned as
-
SW-1054 Loading...