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.
It is not currently possible to change the project key through JIRA's interface. The best way to do this is to:
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.
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.
Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events