nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Project key in repositories URL

Olivier Comeau

Hi, in bitbucket server the project key is in repo url but in bitbucket cloud it is not.

bitbucket server : https://our-proxy.com/scm/PROJECT_KEY/our-repo.git
bitbucket cloud :https://bitbucket.org/our-team/our-repo.git

This means we must have repo names unique by team, is this by design?

Thanks

Accepted answers

Jobin Kuruvilla [Adaptavist]

Yes, it is.

Both are 2 different products, although Stash was renamed to Bitbucket Server to reflect the fact that the core functionality is the same. You can read more about that here but they both vary a lot in the features.

All comments

Jobin Kuruvilla [Adaptavist]

Yes, it is.

Nathaniel Rogers

It's a shame that the PROJECT_KEY is not included in the Bitbucket Cloud repository urls. Is that something in the feature roadmap at all?

Jonathan Valliere

No, it isn't. The Workspace ID is in the URL, not the Project ID. The problem with this is the Workspace ID is global against every other customer using Bitbucket Cloud. Projects are used to group repos but the Project ID (for some insane reason) isn't a part of the repository URL.

Anibal Carracedo

It's a shame, when migrating from Bitbucket Server to the Bitbucket Cloud, you can't search the urls using the project key, also you can't create repos with the same name at the workspace level, in Bitbucket Server you can create repos with the same name and It does not affect it because the project key differentiates them.