Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-9162 Ensure that automated tests around future sprints/plan mode are functioning
  3. JSWCLOUD-9224

Adding issue to a sprint before it is started is considered as a scope change

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Low 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.

              Unassigned Unassigned
              jraoult JonathanA (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: