How can I change a Project Key?

I realize that the Project Key is being used practically everywhere in JIRA as a form of foreign key (the database is not exactly in normal form, is it?).

But maybe someone has a means of changing a key (e.g. from JIRA2011 to JIRA2012), so that all the Issues and Histories and whatever stay with the project.

Or is this another example of "backup to XML, search and replace in XML, restore from XML"?

We are currently running JIRA 4.4.0.

3 answers

1 accepted

8 votes
Accepted answer

Hi All,

Just a quick update, it is now possible to rename the project key via UI in JIRA 6.1

https://confluence.atlassian.com/display/JIRA/Editing+a+Project+Key?from=SvEC

Cheers,

It is not currently possible to change the project key through JIRA's interface. The best way to do this is to:

  1. Export your JIRA data to XML.
  2. Go through the file and replace the instances of the project's key:
    • in the 'key' attribute of the Project entity
    • in the 'key' attribute of all Issue entities.
  3. Search for the project key in the whole XML file. You should not find too many references. Change any that you find.
  4. Rename all attachment folders, as the folder name depends on the project key. This includes one folder for each issue with an attachment, plus one top-level folder for the project.
  5. Reimport your data.
  6. Reindex the data by navigating to Administration -> System -> Indexing and selecting 'Re-Index'.

refered: http://confluence.atlassian.com/display/JIRA/Changing+the+Project+Key

There is a ticket in JIRA for that: https://jira.atlassian.com/browse/JRA-2703

However you can create another project and move all the issues to it, than delete the old one.

Yes and you will find in issue history that previously the issue was in other project with different project key.

Thanks Thomas and Alex - that is what I was afraid of (detour through XML).

Alex, will creating a new project, moving issues, then deleting the old project leave the histories intact?

Does moving the issues from one project to another keep their numbers? It's easy to create a redirection on nginx frontend for fixing old links but the real question is the numbers kept? Remember that you can have spaces between ticket numbers due issues that were removed.

1 vote
Thomas Schlegel Community Champion Feb 15, 2012

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Agile

How Scrum works? It starts with training and education

To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?”  That question applies to both implementation and improvements on the Scrum framew...

196 views 3 5
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