Jira linked to Bitbucket Cloud or Github does not synchronize and show Pull Requests
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
Jira integrated with Github or Bitbucket Cloud does not synchronizes Pull Requests and these are not shown on Development panel, although Pull Requests do mention Jira issue keys. Other information coming from the remote application, like commits or branches, are visible on the ticket.
There are no errors showed in the logs.
Diagnosis
Environment
Jira Software, integrated with Github or Bitbucket Cloud via DVCS integration.
Diagnostic Steps
- Dark feature flag
dvcs.connector.pr-synchronization.disabled onpage<Jira_baseURL>/secure/admin/SiteDarkFeatures!Default.jspais present.
Cause
Pull requests synchronization has bee explicitly disabled via Dark feature flag dvcs.connector.pr-synchronization.disabled (page <Jira_baseURL>/secure/admin/SiteDarkFeatures!Default.jspa), as a part of the workaround described on this knowledge article: DVCS Accounts show sync errors for GitHub repositories in Jira Software
Resolution
- Visit
<Jira_baseURL>/secure/admin/SiteDarkFeatures!Default.jspaand removedvcs.connector.pr-synchronization.disabledflag. - Go to Jira settings > System > DVCS accounts and re-sync the affected repository.
Note
If the Dark feature flag is not the cause and the problem is still present, please raise a case with Atlassian Support.