Rebind Team plan org to different Bitbucket workspace

SonarQube Cloud
1

ALM used: Bitbucket Cloud
Plan: Team plan (paid)

Note: I’m using placeholder names below instead of our real org key and workspace names, since I don’t want to expose our company publicly. Happy to share the real details in a private message or by email.

Problem:
Our SonarQube Cloud organization my-company is bound to a Bitbucket Cloud workspace (bitbucket.org/my-company).

A few months ago, Atlassian ran a mandatory workspace-to-organization linking rollout.
We already had another Bitbucket workspace (bitbucket.org/my-company-dev) linked to our Atlassian organization, so my-company could not also be linked.
As a result, we moved all our code from bitbucket.org/my-company to bitbucket.org/my-company-dev.

We now need to update the SonarQube Cloud organization binding to point to bitbucket.org/my-company-dev instead, but we’re blocked:

  • The Organization Binding page (Administration > Organization Settings > Organization binding) shows “Bound” with no Unbind action, only the text “Binding an organization cannot be undone.”
  • On the Bitbucket side, because my-company was never linked to our Atlassian organization, its Apps and Features / Installed apps section is missing from the workspace settings sidebar.
  • Going directly to bitbucket.org/my-company/workspace/settings/addon-management returns “Resource not found.”
  • So we can’t remove the SonarQube Cloud app from my-company to trigger an automatic unbind, and there’s no unbind control on the SonarQube Cloud side either.

What we’ve tried:

  • Checked Organization binding settings. No unbind control present.
  • Checked Bitbucket workspace settings sidebar for my-company. Apps/Installed apps section is missing.
  • Tried the direct addon-management URL. Got a 404.
  • Confirmed my-company-dev is fully linked to our Atlassian org and works normally.

What we need:
We’d prefer not to create a new SonarQube Cloud organization. We already have billing set up, and starting over means losing our analysis history and extra admin work on our side.

Since this is blocked on Bitbucket’s end and outside our control, could someone from the Sonar team manually unbind our organization and rebind it to the new workspace?

We’d rather not post our real org key and workspace names publicly. Happy to share those details and any other verification you need through a private message, ticket, or email.

2

Hello @jbsilva-hpp,

Thank you for reaching and welcome to the Community.

The typical workflow would be to follow this set of instructions in the documentation:

  1. Remove the SonarQube Cloud app from the GitHub organization or a Bitbucket workspace (this will unbind the organization in SonarQube Cloud). See:
  2. Sign in to SonarQube Cloud.
  3. Bind the unbound organization to the new DevOps platform organization. See Binding an unbound organization for more information.
  4. Change the binding of each project in the SonarQube Cloud organization. See Changing project binding for more information.

But, it seems that’s not available to you due to my-companynever being linked to your Atlassian Organization.

So, a self-service approach isn’t available in this circumstance. I’ve flagged this for our developer team to take a look to see if there’s anything else they can do to avoid recreating the Organization.

Best regards,

Stevan

4

Hi, Stevan
Exactly, the path suggested in the documentation doesn’t apply to the old workspace.

Thank you for escalating this internally!

For reference, the old workspace (left) doesn’t have an “Apps and features” section like the new one (right):

image
image1352×2582 365 KB

5

Hi @jbsilva-hpp,

My understanding is that you lost admin access to the old Bitbucket workspace and you cannot uninstall the app.

I would recommend to:

  • reach out to Bitbucket to get back the admin access so you can uninstall the app
  • follow this path mentioned in our docs:

If the import fails because the organization already exists in SonarQube Cloud and you’ve lost administrator access to this organization, send a request to contact@sonarsource.com with all the necessary details.

7

Hi, Costin
It’s not that. I’m still admin of the old workspace.

8

Are you an Owner of the workspace? According to the documentation only the Owner of personal workspace can manage the applications. See: Apps and features settings are missing for admins in personal workspace | Bitbucket Cloud | Atlassian Support

9

Thanks. I’m not the owner, just a workspace admin.

Anyway, I decided to try again and this time bitbucket.org/my-company/workspace/settings/addon-management went through.
Looks like Atlassian changed something on their end recently and their docs need updating.

I’m glad the Sonar-Bitbucket binding is fixed. However, now I need help getting our previous subscription back: the 200k LOC Team plan we’d had since February 2025.

Since we couldn’t use SonarQube Cloud while the binding was broken, we paused the subscription until it got sorted (either through rebinding or setting up a new org).

The renewal due this past Saturday (August 22) didn’t go through, and we got dropped to the Free plan. I can still see our private projects in the portal, hopefully they won’t get deleted.

I went back to set up billing again, but our plan isn’t listed anymore. The closest match for our 120k LOC is the 300k LOC plan for $200/month, which I couldn’t get budget approval for.

Could you escalate this to your billing/sales team so they can manually reinstate our previous 200k LOC subscription at the rate we were on?

I can provide the org key and any account details by DM or email.

Unfortunately, we won’t be able to continue using SonarQube Cloud without our original tier.

10

I can’t help with that. Could you write an email with the request to contact@sonarsloud.io? Or use SonarQube Cloud Contact Us | Sonar | Sonar?