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

Moving an issue from a current sprint in one project to the backlog of another project causes the sprint from the first project to show up on scrum board of the second project

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Medium Medium
    • None
    • 6.1.4.2
    • AgileBoard

      If you take an issue that is in the current sprint backlog of project A and move it to project B it creates a variety of problems. When you look at the scrum board for project B you will see the sprint name from project A listed in the sprint filter list.

      We are seeing a variety of serious issues with sprints that might be caused by this but we can't be sure. We have had sprints in different project using the same sprint ID. We then had sprints in a project get closed or deleted when sprints with the shared ID in other projects are either closed or deleted. It is creating a great deal of havoc. The only thing we have repro'd reliably is appears of sprint filters across scrum boards.

      Repro:
      Create projects A and B, each with their own scrum boards and backlogs
      Create Project A Sprint 1 and Project B Sprint 1 in the respective boards.
      Add stories to the sprint backlog for project A and start the sprint
      Move a story that is in the current sprint of project A to project B
      View the board for project B

      Results:
      Project A Sprint 1 should be listed on the board for Project B.

      Workaround

      Remove the issue from the Sprint it is in before moving it to the new project. This can also be done after it is moved by looking at Plan Mode, right-clicking the issue, and choosing "Remove from Sprint".

              Unassigned Unassigned
              63606b0b2596 jeffshea
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: