You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
we've done a test migration from Jira/Bitbucket Server to Jira/Bitbucket Cloud. The project keys both in Jira and Bitbucket remained unchanged. Linking Jira Cloud and Bitbucket Cloud seems to generally be ok. Newly created branches and Pull Requests are properly referenced between Jira Cloud and Bitbucket Cloud. The problem is that Pull Requests that were migrated into Bitbucket Cloud are not linked in the corresponding Jira Cloud issue anymore. The other way around, migrated Pull Requests in Bitbucket Cloud do not show the corresponding Jira Cloud issue. The constraints for links between Jira Cloud issues and Bitbucket Cloud Pull requests regarding naming seem to be respected.
How can the references be re-established properly?
We just had this problem (exactly one year to the day) and were able to fix it ourselves by simply going into Workspace Settings > Atlassian Integrations - Jira in bitbucket.org and [Disconnect]ing our Jira Cloud tenant, and then immediately [Connect]ing it, and all PRs, commits, branches appeared almost immediately.
This action requires Admin privileges.
If you are using the DVCS within Jira Cloud, then Jira should be syncing those repos to then look for any references to specific issues keys mentioned in those repos that match any issues in that Jira instance.
In this case, I'd recommend creating a support case in order for our support teams to take a closer look at the specifics of your environment. As the site-admin of a paid site, you can do this yourself by going to https://support.atlassian.com/contact/
I just checked and it looks like you did this over in https://getsupport.atlassian.com/servicedesk/customer/portal/11/BBS-192595