-
Bug
-
Resolution: Duplicate
-
High
-
None
-
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.
When a sprint is started with a delay (set with a time in the future), issues that are removed from it before it starts in fact are shown as "Issues not Completed" on the Sprint Report. The expected behavior would be to have them show up in the "Removed from Sprint" section, or don't show up at all.
Steps to reproduce:
- Create a new sprint from a board, add some issues to it.
- Start that sprint with a delay. For instance, set start date for the next day.
- Remove a few issues from it.
- Check Sprint report, you can still see the issues removed from it in the "Issues Not Completed" section. One would expect them to disappear from the report, or at least show in the "Issues Removed from Sprint" section. On the other hand, Burndown Chart will only start burning data when the sprint starts in fact (the next day).
- End the sprint. Issues are still shown there regardless.
- is duplicated by
-
JSWSERVER-9588 Issues that are completed are showing up as "Removed from Sprint" on the Sprint Report
- Closed
- is related to
-
JSWSERVER-9797 Issue moved out of sprint before start, still shows on reports
- Closed
-
JSWSERVER-9810 rest endpoint "sprintreport" not updated correctly
- Closed
- relates to
-
JSWCLOUD-8029 Sprint Report shows issues that were removed from the sprint in the "Issues Not Completed" section
- Closed
-
JSWSERVER-9790 Sprint Report does not include Story Points added to a Planned Sprint
- Closed
-
JSWSERVER-11334 Sprint report does not include story points added to a started sprint
- Closed
- mentioned in
-
Wiki Page Loading...