Announcing the ability to unlink previously used project keys for reuse

[Carol Low]

@Wendy Imfeld - we've started turning this back on for JSM too. Let us know if you encounter any issues or concerns.

@Tobias Viehweger -

This seems to imply that at the point in time when a project key is released, all existing references will stop working (e.g. in stored JQL queries, issue keys?).

Yes, all statically referenced keys will be affected and will need to be updated.

Would that also affect the normal REST APIs for example?

Indeed it would, but for most of the APIs, there is an option to use ProjectId rather than ProjectKey, in those cases, calls using ProjectId will not be affected - which is what we recommend using.

Let us know if you need more information!

[Gustav Lindskog]

A very nice feature indeed! @Carol Low 
Just wondering: which admin level is this connected to - permission wise?
Is this only changeable by Jira Admins or can a Project Admin also remove the old project key?

/G-man

[Zdeněk]

Absolutely key feature for migrations, thank you! 

[Miriam Hopton]

This is wonderful!! Thank you Atlassian for having this as an option for both team and company managed products. ((happy dance))

I saw the questions about JPD and looking forward to that! We are still in discovery of using JPD in other Atlassian products and have gone through using various project keys /renaming. Looking forward for JPD next! Is there a feature request open link to follow?

[Susan Waldrip]

Hi @Carol Low, just wanted to follow up on the status of reusing project keys in JSM. Is there a ticket for this that we can watch so we don't have to bug you about it? 😁

[Susan Waldrip]

Hi @Carol Low , hope all's well! Just following up on project key reuse for JSM, any idea when it might be available?