Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-19706

Ability to create repositories with the same name

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Implementation of New Features Policy

      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.

            [BCLOUD-19706] Ability to create repositories with the same name

            Ryan Taylor added a comment -

            Check out GitLab. It includes the project/group name in the repo slug.

            Ryan Taylor added a comment - Check out GitLab. It includes the project/group name in the repo slug.

            Rodrigo Porto Riveiro added a comment -

            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!

            Rodrigo Porto Riveiro added a comment - 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!

            yurii.kucherenko added a comment -

            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.

            yurii.kucherenko added a comment - 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.
            Darryl Lee made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 890017 ]
            Dave Parrish [Atlassian] made changes -
            Remote Link Original: This issue links to "ENT-1644 (Jira)" [ 818262 ] New: This issue links to "ENT-1644 (Hello Jira)" [ 818262 ]
            Sam Nichols made changes -
            Remote Link New: This issue links to "ENT-1644 (Jira)" [ 818262 ]
            Prasad Satam (Inactive) made changes -
            Resolution Original: Won't Fix [ 2 ]
            Status Original: Closed [ 6 ] New: Future Consideration [ 11775 ]

            Prasad Satam (Inactive) added a comment -

            We closed this accidentally, we will still be considering this in the future.

            Prasad Satam (Inactive) added a comment - We closed this accidentally, we will still be considering this in the future.

            Sébastien Morin added a comment -

            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 ?

            Sébastien Morin added a comment - 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 ?
            Katarína Lukácsy made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Under Consideration [ 11774 ] New: Closed [ 6 ]

              d74c65c84d35 Prasad Satam (Inactive)
              mabdrahim Syahrul
              Votes:
              35 Vote for this issue
              Watchers:
              39 Start watching this issue

                Created:
                Updated: