-
Bug
-
Resolution: Fixed
-
Low (View bug fix roadmap)
-
None
-
None
-
None
-
None
Create a sprint, add estimated issues then start the sprint. Now, if you go to the burndown chart report you will see that the issues added before you start the sprint are considered as a scope change.
It breaks the test VelocityChartResourceTest#testVelocityWithIssueAddedInSprint so that the expected estimate should be 5 but is 0.
- is detailed by
-
JSWSERVER-9162 Ensure that automated tests around future sprints/plan mode are functioning
- Closed
[JSWSERVER-9224] Adding issue to a sprint before it is started is considered as a scope change
Archived | New: Issue archived |
Epic Link | New: JAGDEV-270 [ 274005 ] |
Parent |
Original:
|
|
Workflow | Original: JAC Sub-task Workflow [ 3433836 ] | New: JAC Bug Workflow v3 [ 3551496 ] |
Issue Type | Original: Sub-task [ 6 ] | New: Bug [ 1 ] |
Link |
New:
This issue is detailed by |
Workflow | Original: GreenHopper Kanban Workflow 20141014 - Restricted [ 1548405 ] | New: JAC Sub-task Workflow [ 3433836 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: GreenHopper Kanban Workflow 20141014 [ 746468 ] | New: GreenHopper Kanban Workflow 20141014 - Restricted [ 1548405 ] |
Workflow | Original: GreenHopper Kanban Workflow v2 [ 536630 ] | New: GreenHopper Kanban Workflow 20141014 [ 746468 ] |
Issue Type | Original: Concern [ 38 ] | New: Sub-task [ 6 ] |
Fix Version/s | Original: 6.2.4 [ 33701 ] |
Fix Version/s | New: 6.2.4 [ 33701 ] | |
Assignee | Original: JonathanA [ jraoult ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Awaiting Deployment [ 10040 ] | New: Resolved [ 5 ] |