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.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Our Bitbucket Workspace was created by a non-personnal account (a shared account called A).
We've added users as "administrators" of this workspace, but when I want to delete the non-personnal account A, it tells me that it will delete all repositories within the workspace.
It seems that the non-personnal account is some kind of "owner" of the workspace, which isn't explicit anywhere on this interface (the account even seems to have additional user rights for example to add apps to the workspace).
How can we transfer the ownership of the workspace?
We, currently have about 490 repos, 175 users, 40 projects and 7 groups.
Migrating repos, all other stuff (users, groups - and its definitions, projects and variables) will not migrate and I will need to do it by hand?
Is that right? Just bc Atlassian can't transform a workspace from personal to shared one?
There is no other way?
When I started setting up the bitbucket.org repos for my company for the first time, it wasn't obvious that the username/WorkspaceID would be tied my own email/loginID during the first-time account creation workflow. I assumed that, worse case, there would be an easy "transfer workspace" option like there is for repos. At this time of my comment here, there wasn't an option to transfer a workspace like this.
I didn't realize I would be able to create additional WorkspaceIDs later after the initial bitbucket.org sign up workflow, and I was worried I wouldn't later have a chance to reserve that URL space for my company. If this was more obvious the first time I interacted with bitbucket.org, I would have created a more "personal" WorkspaceID for own my scratch space - and then immediately added another WorkspaceID for the company after my first login. So, I created the WorkspaceID under my individual human company email address they gave me - which also didn't feel right.
To retain the same URL space, reserving that for my company to "own" so the company doesn't have to keep my email account open after I've moved on to another job, I "transferred" the Workspace/URL like this:
git config --list | grep remote.origin.url and git remote set-url origin firstname.lastname@example.org/... ). my other existing users were using their own bitbucket.org usernames already, so this was just my own locally cloned repo config that needed updating )
Not sure if this is the best/supported way - but the key thing I missed when reading other comments was the emphasis on changing my bitbucket.org username as well as the workspaceID if they were also the same - which, in my case, they were.
There's a knowledge-based article that explains different ways to change Bitbucket Cloud shared workspace ownership.
For the feature/tool to use for transferring workspace ownership, there's an existing feature request for it that can be located through this link. - https://jira.atlassian.com/browse/BCLOUD-22898
You can upvote and watch it for now so that you'll be notified of any updates from our team when the feature becomes available on Bitbucket Cloud.
Please do note that we don't have an exact ETA for the feature request as all new features will be implemented according to our policy here.