This feature is coming.
This is a holdover from the original architecture of Bitbucket. Originally Bitbucket was focused on users collaborating on code projects together and it has grown into teams and organizations collaborating on a large set of shared repositories. All repositories were originally owned by individual users.
Teams were introduced in 2012 so that Teams could share repositories but we still allowed individual users to own repositories, too.
Earlier this year, we introduced Workspaces as a single model of repository ownership. All repositories now belong to Workspaces. To implement this migration from user and team ownership to workspaces we needed to maintain backward compatibility for a time. Therefore, every existing user owns their own workspace. This workspace contains every repository that the user individually owned previously.
We also create a new workspace for every new user due to backwards compatibility of our APIs. The
/users api endpoints still exist but are now deprecated by the
/workspaces endpoint. These legacy endpoints assume that every user has a workspace. When we turn off these endpoints at the end of this year then users will no longer require a workspace and can delete their old workspaces.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
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