Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-6701

Issues retain their sprint information, when moved to another project

    XMLWordPrintable

    Details

      Description

      Scenario:

      1. An issue in an active sprint of project X is cloned
      2. The clone is moved to project Y
      3. The active sprint of project X cannot be closed, because I do not have admin rights for project Y

      Cause:

      It seems the issue is retaining its 'sprint' information, so the active sprint then applies to both project X and project Y. To close the sprint, therefore, the user must either gain admin rights to project Y, or remove the cloned issue from the sprint (in project Y, where no such sprint previously existed).

      Workaround:

      Open the agile board for project Y (or create one if none exists), and you should see a new sprint, named after the active sprint in project X. In this sprint you will find the cloned issue; select the issue and in its preview window, select option "remove from sprint". Do this for all issues cloned from project X; then you can close the active sprint in project X.

      Suggested Solutions:

      1. Issues be stripped of their sprint information, when they are cloned (see GHS-5098); or if that is not possible...
      2. Issues be stripped of their sprint information, when they are moved from one project to another

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                plowry@newbay.com Paul Lowry
                Participants:
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Last commented:
                  6 years, 39 weeks, 4 days ago