-
Bug
-
Resolution: Fixed
-
Low
-
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