Project Becomes Corrupted After Project Key is Changed or New Project is Created

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

After creating or renaming a Project Key, the project with the new key looks to be corrupted and states the project no longer exists. The project and all its information still exists in the database but for some reason JIRA is unable to see the project or know that it exists. This error seems to be related to the following bug:

JRA-38275 - Getting issue details... STATUS

Root Cause

There seems to be a race condition with caches when creating a project or when performing a project key rename.

Resolution

  • Create a brand new project with an arbitrary name and an arbitrary key

Doing this clears up any issues related to the previously renamed project. The renamed project should now come up and have all the information for the renamed project.

Reindexing JIRA is also a known resolution for fixing the problem.

 

Last modified on Feb 26, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.