Changing the Project Key

Following the change of the name of the Team, we would like to modify the project key so that it will also reflect the new team name.

Currently there are 3'000 tickets in the "old" board.

Is changing the key truly harmless, like just edit the project settings, rename, then save?

Any tips/experiences with this amount of tickets?

The instructions say: "Editing a project key is not a trivial task. You should choose key that will suit your long-term needs when creating a project, rather than rely on editing the project key after the project is created. However, there are situations where you need to change the key for an existing project, e.g. change of product name."

Thanks in advance for your help.

2 answers

2 accepted

1 vote

Answer accepted

Hi @[deleted]

Welcome to the Community!!

The effects are

you can still search the issue with old issue keys
Old key won't be released to be used for new projects
Redirects will work perfectly if you still enter the old issue key
JQL and filters will not be affected
If you have referred issues in other Atlassian Applications, those will still continue to work

Here's the full doc

https://support.atlassian.com/jira-cloud-administration/docs/edit-a-projects-details

Thanks,
Pramodh

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you so much for such a fast reply. So this means that we don't have to migrate the old tickets but these will automatically remain on the renamed board?