Not able to browse project after changing project P-KEY

Can you help i am not able to browse project after changing project pkey.

11 answers

2 votes

How did you change the key?

If you did it in the database, you've probably broken your Jira completely and may need to restore from the backup you took before doing it.

But i am able to view all the tickets and create all the tickets

is there a way to change the url to see summary

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)

would it be fine if i change the pkey back to the original?

Change it back or restore from backup, Nic already told you that. Not knowing what you do has always a price.

Only Project P-KEY was changed no other modifications done so if i revert back the update statement executed will that work?

Yes i have changed in Data base but i dont have backup now. Plz let me know any work around or any solution.

Plz let me know what can i do now

If no modifications were done, yes. If not, you may loose some info. As a rule of thumb, ALWAYS do a backup when you decide to dirty up your fingers and do things by hand. And test the modifications on a test system, don't do it directly in the production one.

What you got to loose, now ? Yes.

0 votes

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.

Ok Thanks i shall revert back my changes as per the comments, But is there a way to change the project key?

0 votes

Not directly.

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Agile

What is Scrum? A good, bad, and ugly answer.

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...

63 views 0 1
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you