If a Bitbucket personal workspace and the name of the Bitbucket user whose personal workspace it is do not match, CircleCI is not able to confirm the “Admin” status of any user in the related CircleCI org; even if they are listed as “Admin” in the Bitbucket workspace.
This will result in any actions that require admin-level access not being possible.
Our documentation highlights the requirement for a matching personal/default workspace and username (please refer to the documentation for the Bitbucket Integration).
You will need to identify all users listed as "Admin" of the workspace (https://bitbucket.org/<org_name>/workspace/settings/groups), and have them follow the instructions outlined below.
- Go to your "All workspaces" page (https://bitbucket.org/account/workspaces).
- Click on the workspace for which you don't have the "Leave" option.
- Go to that workspace "Settings" page, and note the
In case the thus obtained
Workspace ID doesn’t match your username, then you'll need to either:
- Change their username or the related workspace name (
Workspace ID) so they match. (Keep in mind that a change to the workspace name will result in a name change for the related org name)
- Transfer the repositories to another workspace that is not a personal/default.
If you want the org name to remain unchanged, you'll need to:
- Create a new workspace with a temporary name.
- Transfer the repositories from the personal/default Bitbucket workspace to that new workspace.
- Change the name of the personal/default Bitbucket workspace (ideally, back to the same name as their Bitbucket username).
- Change the name of the newly created workspace to the previous name (before the above change) of the personal/default Bitbucket workspace you were encountering the issue with.
Article is closed for comments.