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?
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 email@example.com/... ). 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.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events