Will moving repo to different project also move open pull requests?

[Carl_B]

We have a repo at work that everyone uses that is currently under "Project_A". We want to move this repo under a different project name say "Project_B". Looks like the way to do this is to use the "Move Repository" feature under the repo settings as specified here https://community.atlassian.com/t5/Bitbucket-questions/How-do-I-move-a-bitbucket-repo-from-one-project-to-another/qaq-p/949423

I'm assuming this will transfer all the commit history as well, hopefully.

But we also currently have multiple pull requests open under "Project_A". Will using the "Move Repository" also transfer the the pull requests as well as the comment history.

If not is there another way to move the repository to "Project_B" and not lose the comment history on the pull requests. Thanks.

[Theodora Boudale]

Hi Carl and welcome to the community!

Can you please clarify if this is a Bitbucket Cloud repo or Bitbucket Server/Data center repo? Your question has the tag 'bitbucket-cloud' but the question you linked has a screenshot of Bitbucket Server/Data Center in the replies.

The URL of a Bitbucket Cloud repo on browser starts with https://bitbucket.org/ while Bitbucket Server/Data Center repos have a different, custom URL.

If you are using Bitbucket Cloud, do you want to move the repo to another project within the same workspace? Or transfer the repo to a different workspace?

In both cases, the commit history is preserved and pull requests are also transferred. If you move the repo within the same workspace from Project A to Project B (this can be done from Repository settings > dropdown Project), the pull requests of this repo will not show under the pull requests of Project A but under the pull requests of Project B.

If you plan to transfer the repo to a different workspace instead, you need to take into account that the repo URL will change (so you will need to update that in local clones of the repo and any integrations). If the repo uses Pipelines and Deployment variables, these variables are not preserved after a repo transfer to a different workspace, and you will need to write down their values and recreate them after the transfer. Another thing to take into account is that Wiki and Issue Tracker features are not supported in workspaces administered through admin.atlassian.com. These features will be disabled following a transfer to a workspace administered through admin.atlassian.com.

Please feel free to reach out if you have any questions.

Kind regards,
Theodora