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
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
...ollected feedback from users around the lack of shortcuts, and we’re here to address that: In next-gen projects, I miss the keyboard shortcuts badly. This is particularly true on the Board, but also i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event