Old Jira project key reference still exists after creating new project and moving issues Edited

We had issues linked with our DVCS commits incorrectly. there were some old irrelevant commits using JIRA issue references which didn't exist and as new issues with those keys get created the old commits were linked. I followed Pawel's answer from https://community.atlassian.com/t5/JIRA-questions/Can-not-create-jira-project-with-old-edited-project-key/qaq-p/77187


But moved issues rather than export/import. The old issue references via URL still exist even if the old and temporary projects don't. so here's what happened:


1) project with key DS exists

2) project key renamed DSUI in the hopes to break commit links

3) find pawel's answer and create an temp project with key DST

4) move issues from DSUI->DST

5) delete DSUI project

6) Create new project DSUI and move issues from DST->DSUI

7) delete DST project

At this point a DS issue url gets redirected to DSUI.

AFter this issues are still being referenced using DS, DST and DSUI keys. I checked `project_key` table in DB and only the DSUI key exists. However a change history exists in `changeitem` table. the changeitem table does NOT have a row for DS key (since that proj was deleted) but does have rows for rest of the project and key changes. Is this table used for redirection of old issue URLs?

Does the project and issue key change rows need to be cleared out from this table to completely break old references?

2 answers

2 votes
Rachel Wright Community Champion Apr 12, 2017

Hi Atharva,

I haven't expericed the same scenario you described, but maybe I can give you a small lead.  Check the database table called "moved_issue_key".  That's where the DS issue ID to DSUI issue ID mapping lives.

Hope this helps a little bit,

Rachel Wright

That is a great pointer! I feel like there are so many different places where "old" key is mapped now. 

Thanks! I'll give this a try out fo business hours. 

1 vote

This is something that for some reason is well documented for JIRA Server but not for Cloud:



As written in there, another possible workaround (export and re-import the issues):

If you export a renamed project, then import it, it will have the updated project key, i.e. the original project key will not be retained. In fact, all historical keys for that project will be removed. There is a workaround for this that involves changing data directly in your database, see this Answers post.


I have opened the below request to have this information available for JIRA Cloud as well:



I hope this helps.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 13, 2019 in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

624 views 0 12
Read article

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