This question is in reference to Atlassian Documentation: Editing a project key
I ran into a problem were I composed a project which created the project key I had also changed the key. I need to delete the project key associated with this project the reason being I had to create another project with identical name but the project key was conflicting as it said I was trying to use the project key that already existed. Any help with this?
I'm afraid Ravi's answer here is not correct.
Any project keys you create are recorded and kept for historical reasons. JIRA will prevent you from creating a project with an existing key, that makes perfect sense, as you already have a project with that key.
But it will still prevent you from using a key that existed before, even if you change the project key or even delete the original project. It needs a record of removed projects for the history search, so it stops you creating projects with keys that have existed before.
The only workaround is to go into the database and remove the old project key from the table it is stored in. That is only safe to do if you have never created any issues in the dead project, or you have deleted all of the issues that have ever been in it, remembering that it is possible to move issues out of a project and into another one. If you have moved issues out, there's another table you can remove records from, but that does break the history search.
The only workaround is to go into the database and remove the old project key from the table it is stored in.
Seems like that my first-choice database place for keeping the old key (project_key table, project.originalkey field) is not the right place to look for.
Rats! I was creating a new project and wanted to keep the issue prefix. I just got through the Jira admin part 1 and 2 video training modules and swear I saw in there somewhere that you could reuse the prefix in multiple projects. The example was such that all the projects for the DEV team at TIS could use the prefix for each individual project. I will go back through the documentation to see if I can find it.
One cannot change the 'next gen project' to 'classic' one. The only option is to create a new project and move the tickets over.
Drawback (not that there is none yet), we lose the 'key' but have to pick another :-(
Note: Realize that, jira uses this old key to auto reroute to the new key..
i.e. oldticket-1 would now re-route automatically to newticket-1
Confirmed this does work. If the prior project using key = PROJECTX is Deleted, all issues etc. then the key can be reused for a new project.
If PROJECTX is simply rekeyed to, say, PROJECTZ the PROJECTX key will still be attached to the issues. You can run a JQL query "Project = PROJECTX" and it will return a list of issues still associated with the PROJECTX key.
Tested this a couple of times as it is good to know. We could not find clear documentation on this either.
just in case you did not find the answer or if someone else stumbles onto your question, here a post from atlassian:
Feature request that can be upvoted/followed:
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
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events