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

Provide the ability to reuse a project key once its original value is altered

    • 28
    • 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.

      In JIRA 6.x, 7.x, or 8.x, it is possible to rename a project key. However, it is not possible to reuse a project key that was previously used in Jira, even if the original key has been changed.

      Even archiving a Project, Jira will still keep the history of already used keys.

      Current Behavior:

      • Let's say the user has renamed a project key from "ABC" to "KLM"
      • Although there is no project that uses the project key ABC, the user is not allowed to re-use "ABC" for the new project key.

      Suggested behavior:

      • Ideally, the user should be able to re-use the project key "ABC" for other/new project, once the project key has been altered to "KLM".

      Workaround

      • Currently, in order to re-use a project key you need to perform one of the options listed in Editing a Project key: Either delete the project KLM to free up the ABC key, or Export the project and then re-Import it. 

      DO NOT use SQL queries to change DB tables to try to re-use keys.

      This will lead to database inconsistencies as projects are connected to issues, attachments, permissions, workflows, plugins, custom scripts, and etc..

          Form Name

            [JRASERVER-72112] Provide the ability to reuse a project key once its original value is altered

            If a project changes keys, the old key should be available for use without deleting the old project.

            Alexander Hirt added a comment - If a project changes keys, the old key should be available for use without deleting the old project.

            This is cause us trouble as well.  If this key is no longer in use, it should be available.

            Mark Conrad added a comment - This is cause us trouble as well.  If this key is no longer in use, it should be available.

            Tad Foster added a comment - - edited

            The lack of this functionality will cause a problem for large organizations trying to consolidate multiple server Jira platforms into a single data center. With the elimination of Jira server instances in the near future, I'm going to see this as an impediment to bring them over into a single Data Center that is already running hundreds to thousands of project keys already created across multiple instances.

            Tad Foster added a comment - - edited The lack of this functionality will cause a problem for large organizations trying to consolidate multiple server Jira platforms into a single data center. With the elimination of Jira server instances in the near future, I'm going to see this as an impediment to bring them over into a single Data Center that is already running hundreds to thousands of project keys already created across multiple instances.

              Unassigned Unassigned
              gperes@atlassian.com Gregory Peres (Inactive)
              Votes:
              46 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated: