Migrate Classic to Next-Gen and keep the Key Edited

[Roman Balakin]

So we've created a new Next-Gen project and then migrated all the issues to it from Classic. Afterwards we've changed the project key on the old one to a different one(so the old one should've become available) and tried to rename the key on the new next-gen project to the old one. There's an error message still saying that it's not available. Any ideas how to solve this issue? Thank you in advance

[Hernan Halabi _Elite IT Consulting Group_ · Accepted solution]

hello @Roman Balakin welcome to the community, in order to have the key available you will need to delete the old project first.

[Roman Balakin]

Thank you for the answer. It doesn't make much sense to me though, since I've changed the key for old board to a different one.  

[Hernan Halabi _Elite IT Consulting Group_]

The reason is that Jira keeps record of the previous keys so your old links continue to work. As an example let's say you click on an old issue you have on your email. It will have the old key, yet it will sent you to the ticket with the new key in place. Only deleting the project Jira will remove the key from its records