Hello Sonar team,
Sonar Sales Administration directed us to this community for technical assistance.
We use SonarQube Cloud on the EU instance with a Team plan. One private repository has migrated from Bitbucket Cloud to GitHub, while other projects in the same Sonar organization still actively use Bitbucket.
The migrated project’s analyses already run in GitHub Actions and reach the existing Sonar project. However, its ALM binding still points to the retired Bitbucket repository. This has caused a GitHub pull request to be associated with unrelated legacy Bitbucket PR metadata when the PR numbers coincide.
Under Administration → General Settings → Repository binding, we only see Bitbucket repositories and no project-specific unbind option. We have disabled Pipelines for the retired repository. The documented organization-wide migration would affect our other active Bitbucket projects, so it does not fit this partial migration.
Could the technical team clarify the supported path for this single project?
- Can its legacy Bitbucket ALM binding be removed while preserving the project key, analysis history, issues, branches, permissions, visibility, Quality Gate and subscription?
- Can this existing project then be bound to GitHub while the other projects retain their Bitbucket bindings?
- If mixed-platform binding is unsupported, can this project safely remain unbound and continue receiving CI analyses without being associated with the old Bitbucket PRs? What history-preserving alternative is supported?
We are asking for guidance and a project-specific resolution. Please do not migrate the organization, delete/recreate projects, or change our subscription.
I can provide the private project identifiers and verified analysis details directly to a Sonar staff member. Sales Administration advised that the technical team can open a private forum conversation when needed; please initiate one if those details are required.
Thank you.