Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Commits links broken after migration to Jira cloud (issue Key changed)


We did a data centre to cloud migration for a couple of projects using csv import.
We brought 10 on-prem project into 1 cloud project, so the issue key has changed for all 10 projects.

Now the commits links are broken and they are not pointing to the issues in the cloud.

This applies for bitbucket, bamboo and Github.

What would be the best option to relink the tickets?

Thank you

1 answer

0 votes
Andy Heinzer Atlassian Team Jun 10, 2022

Hi Traian,

I understand that you migrated from data center to cloud and at the same time change the project key of many issues.  That will make re-linking these issues extremely difficult if not impossible.  The way Jira links to such development data is via the Jira issuekey being included in the commit title, commit message, branch name, pull request title, pull request description, and alike.

Jira can handle when an issue is moved to a new project within the same site for these redirections.  However because you have changed systems (DC > Cloud) and placed these issues into a new project here, I don't think that kind of redirection would be possible here.  Because Jira did not move these issues from the old project, the redirection cannot be made here.

I understand there were 10 projects consolidated down to one project.  If that consolidation could have taken place within Cloud itself, instead of during the migration, then this might work. But that would require you to import these issues to have the exact same issuekeys in Cloud that they had in Data Center first.  If you can do that, and then link in the development data, it should be functional at that stage.  From there you could then use the bulk change in Jira to move all the issues in say 9 of those projects to one single project if you wish.

I can't feasibly seen another alternative here.  We can't easily make changes to the development data because now it doesn't have a clear link to the new issuekeys to help identify which issue corresponds to new key.

Does that make sense?


Suggest an answer

Log in or Sign up to answer

Community Events

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

Events near you