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

When purging a project from the trash, make that project's key available immediately instead of at the end of the purge

XMLWordPrintable

    • 48
    • 24
    • 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.

      When deleting a project and purging it from the trash, it can take many hours or days for this purge to complete based on the number of issues that are in that project. During that time, the project's key (and any prior keys associated with that project) remain reserved and unable to be reused until the purge completes. 

      This request is to allow any project keys associated with the project being purged from the trash to automatically become available as soon as the purge is initiated.  Perhaps we could immediately randomize all project keys associated with the project immediately upon initiating the purge.

      With the current behavior, if an existing Jira project needs to be re-migrated, you must first delete the project and purge it from the trash.  Once the purge completes, the project key then becomes available, along with any prior project keys associated with that project. 

      This change would allow a project to be remigrated immediately upon initiating the purge of the project from the trash.

              Unassigned Unassigned
              bd3cfc093dfe Sam Lesher
              Votes:
              5 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated: