Create projects with sub-projects
Asked by Christian Fuchs Test 3:

Hello,

is it possible in Bitbucket to create additional projects within projects? We have a lot of repositories, when using only one level, structuring is very confusing and requires a lot of maintenance. It would be nice if there were projects that could contain sub-projects. The repositories could then be located in these sub-projects.

Best regards  
Christian


Answers:
author: Charly [DEISER]
body: Hi Christian,

Unfortunately this is not possible, Bitbucket do not support this kind of hierarchy. This is a heavily requested feature as you can see here: [Can I add sub-project in a project in BitBucket ? (atlassian.com)](https://community.atlassian.com/t5/Bitbucket-questions/Can-I-add-sub-project-in-a-project-in-BitBucket/qaq-p/1317877).

They added the labels feature in bitbucket server/dc which can help you organize the repositories ([Bitbucket Server 5.13 release notes \| Bitbucket Data Center and Server 8.8 \| Atlassian Documentation](https://confluence.atlassian.com/bitbucketserver/bitbucket-server-5-13-release-notes-953131455.html#BitbucketServer5.13releasenotes-Addinglabelstoarepository,availablenowinBitbucketServer5.13)).

Regards!

comments: author: Christian Fuchs Test 3
body: Thanks, unfortunately, we want to use Bitbucket in the cloud, the labels don't help when they works in the server and data center version.  
How do other users structure their repositories when there are dozens of them? Without different levels, we would have dozens of projects next to each other, which is totally confusing.  
How many users / projects / repositories is Bitbucket designed for? Gitlab, for example, can do this much, much better.


author: Charly [DEISER]
body: I totally agree, this is a pain for a lot of people, and right now there is not a single solution that fits all cases. Maybe you can try using the "Workspace" concept ([What is a workspace? \| Bitbucket Cloud \| Atlassian Support](https://support.atlassian.com/bitbucket-cloud/docs/what-is-a-workspace/)), this will allow you to create separate spaces to add your repositories and keep your repositories organized.

Here is the link if you would like to know how to create them: [Join or create a workspace \| Bitbucket Cloud \| Atlassian Support](https://support.atlassian.com/bitbucket-cloud/docs/create-your-workspace/)

Regarding your question "How many users / projects / repositories is Bitbucket designed for?", they have 3 plans (free, standard and premium) which are described here:

[Bitbucket - Pricing \| Atlassian](https://www.atlassian.com/software/bitbucket/pricing)

Regards


author: Lane Maxwell
body: [@Charly \[DEISER\]](/t5/user/viewprofilepage/user-id/551087)

I tried the workspace approach, I would create one for each client I was working for. This worked great for structuring the repositories.  

My structure would be

Workspace (Client Name)

\|----\> Project

\|----\> Repositories.

The drawback to the workspace, and it's a huge one, is that billing occurs at the workspace level. This means that for each client I have, I have to pay for a separate bitbucket plan to have build minutes. I'm moving out of bitbucket and into Gitlab where I can have this billing at an organization level and can organize my repositories into a structure that makes sense.


author: Ulrich Kuhnhardt _IzymesCo_
body: Could you follow a namespace convention for project names? Like Main_project:Sub_project, it would give you at least a logical structure.

It won't be perfect though because there won't be a hierarchy of project, subproject and repository :(

Best, Ulrich


Tags: bitbucket-cloud

cloud