-
Bug
-
Resolution: Fixed
-
Medium (View bug fix roadmap)
-
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 an issue is moved out of a Sprint before starting it (moved to Backlog or another Sprint) when the Sprint is Started, removed issue will still appear on Sprint Report.
Steps to reproduce:
- Create a new Sprint
- Create 3 issues and add them to the sprint
- Move one out
- Start the Sprint
- Look at Sprint Report (the removed issue will be there)
- look at the Burndown report (the Start Sprint event will show only 2 issues, which is correct)
- causes
-
JSWSERVER-9783 Sprint Health Gadget scope change calculation is incorrect
-
- Closed
-
- is duplicated by
-
JSWSERVER-9784 Sprint Report calculation incorrectly includes cloned issues
-
- Closed
-
-
JSWSERVER-9858 Sprint Report shows issues that are not in Sprint
-
- Closed
-
-
JSWSERVER-9810 rest endpoint "sprintreport" not updated correctly
-
- Closed
-
- is related to
-
JSWSERVER-9784 Sprint Report calculation incorrectly includes cloned issues
-
- Closed
-
- relates to
-
JSWSERVER-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
-
-
JSWCLOUD-9797 Issue moved out of sprint before start, still shows on reports
-
- Closed
-
-
JSWSERVER-9854 Issues which are added to a future sprint and resolved before the sprint is started still appear in the sprint
-
- Closed
-
-
JSWSERVER-11334 Sprint report does not include story points added to a started sprint
-
- Closed
-
-
JST-76385 Loading...
- was cloned as
-
JSWSERVER-9919 Issue moved out of sprint before start, still shows on Velocity Charts
-
- Closed
-
- mentioned in
-
Page Loading...
[JSWSERVER-9797] Issue moved out of sprint before start, still shows on reports
Minimum Version | New: 6.03 |
Workflow | Original: JAC Bug Workflow v2 [ 2855738 ] | New: JAC Bug Workflow v3 [ 2937879 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542670 ] | New: JAC Bug Workflow v2 [ 2855738 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549194 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542670 ] |
Description |
Original:
When an issue is moved out of a Sprint before starting it (moved to Backlog or another Sprint) when the Sprint is Started, removed issue will still appear on Sprint Report.
*Steps to reproduce:* # Create a new Sprint # Create 3 issues and add them to the sprint # Move one out # Start the Sprint # Look at Sprint Report (the removed issue will be there) # look at the Burndown report (the Start Sprint event will show only 2 issues, which is correct) |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-9797]. {panel} When an issue is moved out of a Sprint before starting it (moved to Backlog or another Sprint) when the Sprint is Started, removed issue will still appear on Sprint Report. *Steps to reproduce:* # Create a new Sprint # Create 3 issues and add them to the sprint # Move one out # Start the Sprint # Look at Sprint Report (the removed issue will be there) # look at the Burndown report (the Start Sprint event will show only 2 issues, which is correct) |
Link |
New:
This issue relates to |
Labels | Original: affects-server fixme future_sprints | New: affects-cloud affects-server fixme future_sprints |
Labels | Original: fixme future_sprints | New: affects-server fixme future_sprints |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 908601 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549194 ] |
Workflow | Original: GreenHopper Kanban Workflow 20141014 [ 746857 ] | New: JIRA Bug Workflow w Kanban v6 [ 908601 ] |