Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-31260

Bulk move issues will ignore the issue key sequence in the source project

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      When bulk moving issues from one project to another, the original sequence of the issues issue key will be lost during the process.

      As an example, I've created 2 projects (Source Project and Target Project), and created 10 test issues under Source Project:

      After bulk moving all 10 issues to the Target Project, the original sequence of the issue key is lost, seems like the new issue key are randomly assigned to those issues:

      Hence, it will be great if the original issue key sequence is retained when bulk moving issues, or at least give the user an option to choose the original sequence or not.

        1. targetproject.png
          targetproject.png
          95 kB
        2. sourceproject.png
          sourceproject.png
          104 kB

              Unassigned Unassigned
              afaisal Ahmad Faisal (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: