Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Migrate Classic to Next-Gen and keep the Key


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

1 answer

1 accepted

0 votes
Answer accepted

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

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.  

Like ashley.frost likes this

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

Like Roman Balakin likes this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events