Jira Cloud-to-Cloud Migration and Bitbucket Development Information

Likhita Biyyala

Hi Community,

We are planning to perform a Jira Cloud-to-Cloud migration between two Atlassian cloud organizations.

• The source Jira instance is integrated with Bitbucket, and development information (commits, branches, and pull requests) is visible in the Development section of Jira issues.
• The target organization uses GitHub, but GitHub is currently not integrated with Jira and they might plan in future.

After the Jira migration, will the development information from Bitbucket remain visible in the migrated Jira issues, or is only the core Jira issue data migrated? If yes, what will be the impact.

Thank you in advance for any guidance or experience you can share.

Abaho Katabarwa (Katabarwa Labs)

Hi @Likhita Biyyala, to add to Ashish's answer, the development panel can usually be brought back after the migration rather than lost for good.

The commits, branches and pull requests live in Bitbucket and are matched to Jira by the work item keys in commit messages and branch names. Once the target site is connected to your Bitbucket workspace (in Bitbucket: Workspace settings > Atlassian integrations > Jira, connect the new site), Bitbucket sends that information to the new site, and work items whose keys match show their development information again. This only lines up if the project keys and work item numbers stay the same in the target site, so check that in your migration plan.

If the panel doesn't populate after connecting, disconnecting and reconnecting the site in the same Bitbucket settings page is a commonly reported fix. I'd test it on one project first before the full cutover.