No idea, you have not answered the question
Before we can give you any useful help, we need you to answer the question I asked and tell us how you changed the key. (And seriously, if you did it in the database, then make sure you have your backup ready for restoration)
Make sure you take Jira offline while you change the data back.
When you've done this, I'd strongly recommend re-indexing the system immediately after you restart it, and then running the integrity checker afterwards.
If you're lucky, you won't have too much damage and those two steps will leave your system stable and working.
There is a whole batch of SQL you can execute to change the project key, but you have to do it all offline, with backups, reindexing, integrity checks etc. You need to be immensely careful what you change to catch everything - off the top of my head (I know there's more than this), issues, project table, project custom keys, workflows, filters, comments, descriptions, raw text fields...
The standard way to change a project key is to create the new project, and then move any issues you want to use into it. That's completely supported and won't trash your system.
In a world of dark-scrum, faux-scrum, and scrum-butt, the question still remains: What is scrum and how do you do it “right?” That’s the question we set out to answer. I'm Max, I've been teaching c...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs