Hi is there anyway to change a project key and all the issue key associated to the project? This is one way to do it, but is there any easier way? This involves too many steps and time consuming if the JIRA is big. * Export your JIRA data to XML. * 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. * Search for the project key in the whole XML file. You should not find too many references. Change any that you find. * 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. * Reimport your data. * Reindex the data by navigating to Administration -> System -> Indexing and selecting 'Re-Index'.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA change project key

Pangianto Pang

Hi is there anyway to change a project key and all the issue key associated to the project?

This is one way to do it, but is there any easier way? This involves too many steps and time consuming if the JIRA is big.

Export your JIRA data to XML.
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.
Search for the project key in the whole XML file. You should not find too many references. Change any that you find.
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.
Reimport your data.
Reindex the data by navigating to Administration -> System -> Indexing and selecting 'Re-Index'.

Accepted answers

Jobin Kuruvilla [Adaptavist]

This is the most effective solution. If you do it in DB, there may still be references hanging around and it won't fix attachments.

All comments

Jobin Kuruvilla [Adaptavist]

This is the most effective solution. If you do it in DB, there may still be references hanging around and it won't fix attachments.

Pangianto Pang

another workaround is to create a new project with the same configuration as the old project but edit the project key.

do a bulk move issues from old project to new project

Danilo Conrad

This feature was implemented on JIRA 6.1 (see release notes), and it is now possible to change project key via the JIRA UI. For the detailed instructions about this feature, you may refer to the links below:

Cheers,

Danilo

James Guerin

Warning to future admins using this feature: editing the project key in JIRA does not migrate attachments nor does it create a new project key attachment directory (even for new issues after renaming).

This could be important if you have additional web services accessing files in the Jira attachment directory based off the project key (like I did).

Deepak Raja M

Thats well said

mbrock

Hello, I have changed a Next Gen project name from IT to OLDIT. The Project Key shows as OLDIT now - hwever - when I try to create a Classic Project called IT and specify using IT as the Project Key, I'm told that "Old IT Support uses this Project Key". How do I accomplish creating my new Classic Project with the Project Key I love?