Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-17687

When completing a sprint, if an issue is assigned to that sprint, but is not displayed on the board (due to status mappings), that issue is incorrectly added to the next future sprint.

    XMLWordPrintable

Details

    Description

      Issue Summary

       

      Raising a bug that is described by amerlino on her internal Confluence page.

      Steps to Reproduce

      1. Create a Scrum board that has 4 statuses: To Do, In Progress, Done, Closed
      2. Create & start a sprint "Sprint 1" with two issues in it.
      3. Transition one issue all the way to "Closed".
      4. Modify the status-column mapping of the board to unmap the Closed status.
      5. Create a future sprint on the backlog.
      6. Complete the sprint.
      7. View the issue which was transitioned to Closed.

      Expected Results

      The issue which was Closed should only be assigned to one sprint - Sprint 1.

      Actual Results

      The issue is assigned to Sprint 1 (the completed sprint) and the future sprint. This is visible on the issue view page, but not in the backlog, because the Closed status is not mapped to any column of the board.

      Workaround

      Ensure that all statuses are mapped to a column before completing sprints to prevent issues being tacked onto any future sprints.

       

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mtokar Michael Tokar
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: