NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

Hi everyone,

Thanks so much for your votes and comments on this feature request.

On May 13th we made the announcement that JIRA will no longer support unlimited customisations of the project key. From JIRA 6.1 we are only going to support customised project keys that meet all of the conditions specified below:

1. The first character is a letter from the Modern Roman Alphabet
2. The first and all consecutive letter characters are in upper case
3. Only letters, numbers or the underscore character is used

We understand that some customers may be in the position where their current project keys do not meet the above requirements. We want to help these customers migrate to a supported format. To do this, we will implement this highly-voted feature request to allow the editing of project keys. We have started work on this and we aim to complete it for the JIRA 6.1 release. Given that it is very early in the release cycle we can not guarantee this and we will keep everyone updated via this issue.

For customers that cannot wait until the 6.1 release, the current recommended workaround is to create a new project and use Bulk Move to transfer issues over from the old project to the new project. This has the additional benefit of providing redirection from the old issue key to the new issue key if anyone has an external reference to it. We realize that there is still manual work involved with moving components and versions and other project configuration.

Thanks for your patience and we hope you appreciate our open approach to feature requests.

Cheers,
Bartek
JIRA Product Management
bartek (at) atlassian (dot) com