-
Bug
-
Resolution: Duplicate
-
High (View bug fix roadmap)
-
None
-
6.3.0.2
-
None
-
6.03
-
Reproduce:
- Create a sprint and assign some issues to it.
- Clone one of the issues and move the cloned issue back to the backlog
- Start and complete the sprint
- The sprint report mentions the cloned issue as not completed in the issue table
Problem is in BurndownUtils#addSprintHistoryChanges method. The code makes the assumption that the first change the sprint custom field value of an issue is setting the value to a sprint, not removing it, as is the case with the cloned issue. This causes the the cloned issue to be counted as being part of the sprint, while it was not.
- duplicates
-
JSWSERVER-9797 Issue moved out of sprint before start, still shows on reports
-
- Closed
-
- relates to
-
JSWSERVER-9797 Issue moved out of sprint before start, still shows on reports
-
- Closed
-
[JSWSERVER-9784] Sprint Report calculation incorrectly includes cloned issues
Minimum Version | New: 6.03 |
Workflow | Original: JAC Bug Workflow v2 [ 2855347 ] | New: JAC Bug Workflow v3 [ 2937666 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542295 ] | New: JAC Bug Workflow v2 [ 2855347 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548707 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2542295 ] |
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 [ 908685 ] | New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1548707 ] |
Workflow | Original: GreenHopper Kanban Workflow 20141014 [ 746927 ] | New: JIRA Bug Workflow w Kanban v6 [ 908685 ] |
Workflow | Original: GreenHopper Kanban Workflow v2 [ 555193 ] | New: GreenHopper Kanban Workflow 20141014 [ 746927 ] |
Sprint | Original: Finish Coathanger [ 824 ] |