• 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.

      Issue Summary

      We would like to be able to delete pull requests so they are fully removed from the repository.

      Workaround

      1. If you are a paying customer, you can reach out support team and request deleting a pull request.
      2. If you don't mind the pull requests remain in your repository, you can decline them.

       

      IMPORTANT:

      If you are looking to delete a pull request because sensitive information was published in a pull request, please read this article. It is important to realize that deleting a pull request will not remove sensitive data from your repository.

      https://confluence.atlassian.com/bbkb/what-to-do-if-you-ve-committed-sensitive-data-to-a-bitbucket-cloud-repository-1168857188.html

      Please upvote this issue only if you are interested in this feature outside of trying to remove sensitive data from your repository.

            [BCLOUD-22181] Add support to Delete a Pull Request

            Chase Jones added a comment -

            +1

            Chase Jones added a comment - +1

            +1

            Shaun Chan added a comment - +1

            georgh added a comment -

            +10

            georgh added a comment - +10

            +1

            Jan Bongers added a comment - +1

            +1

            Given that Bitbucket Server (and presumably Data Center too) have the ability to delete a PR, going to Cloud shouldn't give me less options.   Asking only for (at least) feature-parity w/the now-eol software you used to have.

             

            Paul Hirose added a comment - Given that Bitbucket Server (and presumably Data Center too) have the ability to delete a PR, going to Cloud shouldn't give me less options.   Asking only for (at least) feature-parity w/the now-eol software you used to have.  

            +1

            James Brundell added a comment - +1

            aron.beal added a comment -

            If you have a branch that you need to keep open in perpetuity (e.g. `develop`), and you inadvertently open a PR against that, you've no way to get rid of it.  It lives in perpetuity on the right side of the interface when viewing the branch.

            aron.beal added a comment - If you have a branch that you need to keep open in perpetuity (e.g. `develop`), and you inadvertently open a PR against that, you've no way to get rid of it.  It lives in perpetuity on the right side of the interface when viewing the branch.

            ccenvcvb added a comment -

            We found that the pull request preview is unreliable in showing what would be merged, you need to actually create the pull request to see that. This was the case in server and I don't expect that to behave differently in that regard. pull requests made for that reason are more often than not unwanted. 

            Deleting unwanted pull requests is just a matter of keeping the overview of pull request clean. 

            Yet Another Server Feature missing after the cloud migration downgrade. I can understand the cloud move but missing features like this should have priority.

            ccenvcvb added a comment - We found that the pull request preview is unreliable in showing what would be merged, you need to actually create the pull request to see that. This was the case in server and I don't expect that to behave differently in that regard. pull requests made for that reason are more often than not unwanted.  Deleting unwanted pull requests is just a matter of keeping the overview of pull request clean.  Yet Another Server Feature missing after the cloud migration downgrade. I can understand the cloud move but missing features like this should have priority.

              Unassigned Unassigned
              1a12696570a5 Arun Ravikumar
              Votes:
              185 Vote for this issue
              Watchers:
              73 Start watching this issue

                Created:
                Updated: