BitBucket Repository Organizational Structure

[George_Weber]

I looked around the documentation and help answers for awhile but could not find an exact answer to an organizional question.

We currently have a team account in which several groups have access. Ideally, we would like to have one team account, and on the main team page would be several directories, such as Group A, Group B, etc. Then, if you enter the Group A directory, multiple repositories would be stored (one for fortran code, one for C++ code, one for general information, etc.) A member of Group A could therefore just work within the one directory. However, they sometimes need read/write access to another group's repository. So in that case, they could back out into the main team account and enter the different directory where all the repos for this directory are held.

The main problem we are trying to avoid is having a dump of repositories on the main team account that belong to different groups. For example, Group A and Group B would both have separate directories for Fortran Code, but sometimes a member has access to both these repos. So if the repos are on the same hierarchial level, it can become confusing and disorganized.

Is there a way to implement such a structure in BitBucket? Or is there an equivalent alternative?

Thank you

[George_Weber · Accepted solution]

So it looks like this structure is not possible as of this time. I found that it is a highly prioritized topic on the issue board:

https://bitbucket.org/site/master/issue/2323/create-a-way-to-group-repositories

A comment on the topic (10/7/2013) implies that the issue may be resolved soon.

Official update:

We are currently exploring various design options for ways to group repositories on Bitbucket. This item will be on our short term roadmap with an expected delivery sometime after the start of the new calendar year.

Cheers, Justen -- Bitbucket product manager

[Anton Anisimov]

When? It is 2015 in my country

[Anton Anisimov]

Finally they did it!!

https://confluence.atlassian.com/bitbucket/projects-792497956.html?utm_source=product-release-email&utm_medium=email&utm_campaign=BB-3PO

[jswinborne]

Kind of.  Yes you can group your repos into projects, but the project name is not part of the path to the git repo.  So if you have a project named "Client 1" with a repo named "website", and you try and create another project named "Client 2" with a repo named "website", you will be told you already have a repo named website.  it is a bummer that project name isn't in the repo address.  That said the project feature is definitely an improvement, and I appreciate it!

[Justin Wilson]

[Sree]

Is this feature available yet?

[Rich Warwick]

Any update on this upcoming feature? It is well after the first of the year.

[Sebastiaan Blommers]

I'm also very interested in a good group-repo solution. We are stacking up a lot of repo's currently, would be nice if they could be grouped up just like in Rhodecode.

[priyang]

Team, any progress on this? we are also facing similar issue. 

[AgentSmith]

From our documentation:

Your team administrator can create groups whose members are individual account holders. Team members can create repositories and make the team an owner. Repositories owned by the team appear on the team dashboard.

Bitbucket adds a team's groups automatically to new team repositories. Repository administrators can give repository access to individual accounts or other groups that are not team members.

Account holders with access to a team's private repositories count toward the team plan.

With that, there are two main things you cannot do with Teams:

1. You can't create a group that has a team as it members.

2. You can't reference repositories owned by other teams; hierarchies of teams aren't supported.

This is all explained in more detail, along with illustrations here:

https://confluence.atlassian.com/display/BITBUCKET/Teams+and+repos+and+groups

[George_Weber]

Sorry, Jason. I meant to say in the opening post that I had read this page of the documentation. This is where my questions arose from.

I was wondering if there was any way to structure the team account in the manner previously stated. Or is it the case that there is no way to form some kind of directory of repositories?