-
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
-
BCLOUD-13202 Allow user to manage repositories access with Project Permissions
- Closed
-
ENT-1644 Loading...
- Wiki Page
-
Wiki Page Loading...