Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-20206

Completing a sprint only moves incomplete issues to next sprint if the issue is in the board

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 7.12.3, 8.3.2
    • Sprint
    • None

      Issue Summary

      When completing a sprint in Jira not all incomplete issues are moved to the selected sprint.

      Steps to Reproduce

      1. Create a project with two boards
      2. Set one of the boards to only one issue type (e.g. Bug)
      3. Create two sprints and add one issue of each type to each sprint
      4. Start the sprint
      5. On the board with only one issue type, complete the sprint and select to move all issues to the second sprint.

      See complete_sprint.mov

      Expected Results

      • All issues in that sprint would be migrated to the new Sprint
      • Or Jira would show a message stating that X issues would not be moved as they are not part in the board.

      Actual Results

      Jira shows:

      X issues were incomplete
      Select where all the incomplete issues should be moved:

      but only moves the sub-set of issues that are present in the board.

      Workaround

      • Manually bulk-edit the issues after completing the sprint.
      • Or have a board with all issues in the sprint included, and complete the sprint from this board.

        1. complete_sprint.mov
          6.43 MB

            [JSWSERVER-20206] Completing a sprint only moves incomplete issues to next sprint if the issue is in the board

            CHD CM Support added a comment -

            The workaround #1 is not usable in "real-life", as you will kill the sprint history of the issues (see JSWSERVER-13333), so this issue should have a higher severity as it costs us ~2-3 hours of manual effort every two weeks since March 2019 when this issue showed up first at our organization.

            CHD CM Support added a comment - The workaround #1 is not usable in "real-life", as you will kill the sprint history of the issues (see JSWSERVER-13333 ), so this issue should have a higher severity as it costs us ~2-3 hours of manual effort every two weeks since March 2019 when this issue showed up first at our organization.

              Unassigned Unassigned
              mfernandes@atlassian.com Matheus Fernandes
              Affected customers:
              3 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated: