Development Field Not Updated After Project Migration Using Jira Cloud Migration Assistant

[Ari Raatikainen]

Hello,

I am trying to migrate one project from Jira cloud site A to another Jira cloud site B using the Jira Cloud Migration Assistant. The project has a GitHub for Jira integration set up to display development-related data (such as commits, branches, pull requests) in the "Development" field within issues.

However, after completing the migration, I noticed that the Jira project field "Development" on site B is not showing the expected data. It seems like the development-related data has not been migrated or re-synced correctly.

Do you know, and looking for help with the following:

1. Is the GitHub for Jira integration expected to re-sync development data automatically after migration, or are there additional steps needed post-migration to ensure that this data appears in the "Development" field?
2. Can I manually trigger a re-sync of development data from GitHub after migration?

Thank you in advance for your help!

[Marc - Devoteam]

HI @Ari Raatikainen 

On both question the answer is sadly no.

You will need to setup the GitHub integration on site B as the connection is initiated from GitHub.

Also, as far as I know the Jira Development integration uses issue keys to map the field.

So as long as the issue keys in your other instance aren't identical to the original keys you probably can't map your existing GitHub integration to the new instance/project.