-
Bug
-
Resolution: Fixed
-
High
-
6.3.0.2
-
None
-
6.03
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Steps to reproduce
- create a Planned Sprint;
- add Issues to the new Sprint;
- add or edit Story Points in those Issues;
- start the Sprint.
Expected result
The Story Points values existing at the moment the Sprint was started are accounted for in all reports.
Actual result
Sprint Report displays no Story Points ( - ) for Issues that had the value changed after they were added to a Planned Sprint, but before it was started. Burndown Chart shows correct values.
- is duplicated by
-
JSWSERVER-9820 Completed Issue Type = Story point values are not showing up in Sprint Report nor Velocity Report
- Closed
-
JSWSERVER-9785 Sprint Report showing story points in '-' (hyphen) values before sprint start
- Closed
-
JSWSERVER-9824 In the Sprint Report, an issue shows Story Points as - if the story point value has changed after the start of the sprint
- Closed
-
JSWSERVER-8169 Sprint Report lists incorrect starting story points
- Closed
- is related to
-
JSWSERVER-8029 Sprint Report shows issues that were removed from the sprint in the "Issues Not Completed" section
- Closed
-
JSWSERVER-9797 Issue moved out of sprint before start, still shows on reports
- Closed
-
JSWSERVER-9824 In the Sprint Report, an issue shows Story Points as - if the story point value has changed after the start of the sprint
- Closed
- relates to
-
JSWCLOUD-9790 Sprint Report does not include Story Points added to a Planned Sprint
- Closed
-
JSWSERVER-9783 Sprint Health Gadget scope change calculation is incorrect
- Closed
- was cloned as
-
JSWSERVER-11334 Sprint report does not include story points added to a started sprint
- Closed
- mentioned in
-
Page Loading...