Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-31260

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

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? 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. sourceproject.png
          sourceproject.png
          104 kB
        2. targetproject.png
          targetproject.png
          95 kB

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

                Created:
                Updated:
                Resolved: