-
Suggestion
-
Resolution: Unresolved
At the moment, we can't set an ETA for this feature to be released, since there's a number of factors that determine how our product team prioritizes new features. Consider adding yourself as a watcher to be kept informed as to the state of this feature request moving forward. With that way, if our development team updates the ticket, you'll be notified via email.
You can learn more by reading Implementation of New Features Policy.
Problem Definition
Currently, Bitbucket repositories don't have unique ID hence the user is unable to create repositories with the same name even if it's on different projects because all repositories are accessed within the level of workspace. As Bitbucket Server guarantees the repository name to be unique per project, this constraint impedes the server-to-cloud migration.
Suggested Solution
Allow the users to maintain the uniqueness of repository names per project.
Workaround
None. Consider adding yourself as a watcher to be kept informed as to the state of this feature request moving forward. With that way, if our development team updates the ticket, you'll be notified via email.
- relates to
-
- Closed
-
ENT-1644 Failed to load
- Wiki Page
-
Wiki Page Failed to load
[BCLOUD-19706] Ability to create repositories with the same name
Hi,
In our opinion, this is a crucial improvement, as many companies are likely facing the same challenge. It seems logical that, just as there is project-level isolation for permissions, there should also be isolation for repository names.
This limitation is currently causing issues for us, and we believe that enabling repository name uniqueness per project would greatly enhance repository organization and migration processes.
Could you share any updates on whether this feature is being considered for future development?
Thanks!
Our migration from Bitbucket DC to Bitbucket is currently blocked by this feature. We have too many repositories with duplicate names across numerous projects in DC and renaming them will have a significant impact on development process.
Possibly, we will have to cancel our migration to the Cloud until duplicate repository names in different projects are supported, unless some sort of workaround appears.
We closed this accidentally, we will still be considering this in the future.
So a good portion of the Roadmap is to actually make the Projects more then a placeholder but the possibility of creating repository with the same name in multiple Projects is so out of scope that it ends up being marked as Won't Fix ?
We have reviewed our priorities for this year and this is unfortunately not something we are able to prioritize right now. You can find our public roadmap here: https://www.atlassian.com/roadmap/cloud?selectedProduct=bitbucket)
Moving this to "Under Consideration" because we are definitely considering how to implement and the potential impacts.
We are in the process of expanding what Projects in Bitbucket Cloud can configure. We want to allow users to manage permissions at the Project Level as well as configure settings across all repositories in a project.
As we do this work the ability to restrict repository namespace to a project is definitely something we want to consider.
Adding this could potentially impact remote urls as we add another layer.
Our integrated CICD and automation toolsets are significantly impacted (if we were to transition from Server to Cloud variant) by the absence of this capability. The change impact is detrimental to a view to transition to cloud.
Additionally some of our automation tools require to utilise the APIs at project level; not team or repository level. Hence we have conflicts here too.
This will prevent our ability to transition to cloud.
Check out GitLab. It includes the project/group name in the repo slug.