Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-3751

Allow historical aliasing of projects and repositories

XMLWordPrintable

    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Stash currently allows renaming repositories and projects. However if this is done, all users who have cloned the repository or bookmarked the web URL will have update them accordingly and get no prompt or information as to where it exists now.

      Stash should keep a record of original project keys / repository slugs when operations are performed which can changed them. It could then provide a redirect in the browser amd output the git remote set-url command to use when attempting to clone/fetch/push to with an old url.

          Form Name

            [BSERV-3751] Allow historical aliasing of projects and repositories

            JP Mariano made changes -
            Remote Link New: This issue links to "Page (Atlassian Documentation)" [ 797928 ]
            Aedrian Escultura made changes -
            Link New: This issue is related to BSERV-10230 [ BSERV-10230 ]

            mark-1003 added a comment -

            Is there any documentation about this feature available?

            • How does it work?
            • In which cases is there a redirect to the old URL? Everytime?
            • How long does this redirect exist?
            • Is there a page where all active redirects can be seen?
            • ...

            mark-1003 added a comment - Is there any documentation about this feature available? How does it work? In which cases is there a redirect to the old URL? Everytime? How long does this redirect exist? Is there a page where all active redirects can be seen? ...

            Oliver Zabel added a comment -

            Hi, so i tested this with Bitbucket Server 6.4.3 and it seems to work. Nevertheless there is a problem left.

            Assume that you moved a repo A from Project X to Y.

            It turns out, that you can create an new repository B in X with the name of project A. So the clone URL will have the exact same name as repo A had before moving it to Y and where it is still pointing to. 

            The newly created repo B cannot be accessed since the URL is pointing to A.

            In my point of view, Bitbucket should not allow to create a repo in X with the name of A OR needs to alter the clone url.

            Oliver Zabel added a comment - Hi, so i tested this with Bitbucket Server 6.4.3 and it seems to work. Nevertheless there is a problem left. Assume that you moved a repo A from Project X to Y. It turns out, that you can create an new repository B in X with the name of project A. So the clone URL will have the exact same name as repo A had before moving it to Y and where it is still pointing to.  The newly created repo B cannot be accessed since the URL is pointing to A. In my point of view, Bitbucket should not allow to create a repo in X with the name of A OR needs to alter the clone url.
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3396799 ] New: JAC Suggestion Workflow 3 [ 3620846 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: BSERV Suggestions Workflow [ 2683158 ] New: JAC Suggestion Workflow [ 3396799 ]

            David Deutsch added a comment -

            I see this was resolved a couple years ago in version 5.0, but for the life of me I cannot find out how it was resolved, i.e. how do I move a repository to a different project while keeping the old URL? All of my attempts at Googling have only led me to tickets such as these, and I haven't seen anything jump out of me from the official documentation. FWIW, it would be helpful for all resolved "feature suggestion" tickets if they linked to the relevant documentation. 

            David Deutsch added a comment - I see this was resolved a couple years ago in version 5.0, but for the life of me I cannot find out  how it was resolved, i.e. how do I move a repository to a different project while keeping the old URL? All of my attempts at Googling have only led me to tickets such as these, and I haven't seen anything jump out of me from the official documentation. FWIW, it would be helpful for all resolved "feature suggestion" tickets if they linked to the relevant documentation. 
            Caterina Curti made changes -
            Link New: This issue is related to BSERV-11048 [ BSERV-11048 ]
            Owen made changes -
            Workflow Original: Stash Workflow [ 549841 ] New: BSERV Suggestions Workflow [ 2683158 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Michael Studman (Inactive) made changes -
            Fix Version/s New: 5.0.0 [ 66696 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Quality Review [ 10029 ] New: Closed [ 6 ]

              mheemskerk Michael Heemskerk (Inactive)
              jhinch jhinch (Atlassian)
              Votes:
              44 Vote for this issue
              Watchers:
              31 Start watching this issue

                Created:
                Updated:
                Resolved: