Grouping projects and repos
Asked by Eric:

I have a group of projects and repos that I have been added to (as a read/write contributor) and some of them have the same names as projects that I already have in my workspace.

Is there a way to group these other projects into a common list? Creating a Project and adding them into the subproject would be ideal, but that doesn't appear to be possible.

There was a Label feature added 2 years ago, but I can't find it in the current UI, so I suspect it has been remove: <https://confluence.atlassian.com/bitbucketserverkb/known-limitations-of-the-repository-labels-993923225.html>

Any other options for keeping things organised?


Answers:
author: Caroline R
body: Hi, [@Eric](/t5/user/viewprofilepage/user-id/4827590), welcome to the community!

Currently, the structure we have in Bitbucket is **Workspace \> Projects \> Repositories**. Unfortunately, we don't have subprojects yet.

If you open a Workspace \> Projects, you will only see the projects within this workspace. However, if you go to the [Projects dashboard](https://bitbucket.org/dashboard/projects), you will see all the projects that you have access to, which I believe is the path you are following and the reason why you would like to have subprojects, is that correct?

If that's the case, I have two recommendations that might help you:

1. You can access the workspace **and then** the projects within this workspace so there is no confusion regarding your personal projects;

2. A workaround would be to update the avatar of your personal projects, that way you can differentiate them from the others.

   **a.** In order to update it, open your project \> go to **Project Settings** \> **Change Avatar:**

![Screen Shot 2022-09-13 at 5.32.36 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/215860i285C44D4138F64D1/image-size/large?v=v2&px=999 "Screen Shot 2022-09-13 at 5.32.36 PM.png")

We do have some feature requests to add subprojects to Bitbucket Cloud:

* <https://jira.atlassian.com/browse/BCLOUD-18277>

* <https://jira.atlassian.com/browse/BCLOUD-21218>

I would suggest that you add your vote there (by selecting the **Vote for this issue** link) as the number of votes helps the development team and product managers better understand the demand for new features.

You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the **Start watching this issue** link) if you'd like to get notified via email on updates.

Implementation of new features is done as per our policy [here](https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html) and any updates will be posted in the feature request.

The link you shared about labels is related to Bitbucket Server, so it doesn't apply to Bitbucket Cloud.

I hope this helps, but please feel free to share any additional questions or concerns regarding this case.

Kind regards,  
Caroline

comments: author: Eric
body: Thank you for the reply.

I have a 8 different repos in 3 separate workspaces and 3 different projects that were handed over to me with read/write access. Some of the project have the same names (which are mandated by project management), so it gets confusing quickly.

Ideally, I would create a new Project and put these Repos into the new Project, but creating a new project and clicking on "Add repositories" actually moves the repo to that project which requires admin access. It appears that there is a 1:1 relationship between a Project and a Repo, whereas I would expect a repo containing a library could be included in multiple projects.

I've voted for <https://jira.atlassian.com/browse/BCLOUD-21218>. The existing organisational method for Bitbucket definitely needs to be improved to be useful for large projects.


Tags: bitbucket-cloud

cloud

label