Bitbucket Cloud is removing the “Update pull request” page

[#1]

Hi Bitbucket community,

We have a small announcement to share about a change we’re making to streamline Bitbucket Cloud.

What is changing

Beginning the week of June 24, we will be removing the Update pull request page. There will no longer be an “Edit” option on pull requests, and any requests to a PR’s Update page will automatically be redirected to the main page of the pull request.

Functionality that is being removed

With this change, we are removing the ability to add suggested reviewers when updating a pull request. All other functionality available on the Update page is now available on the main pull request page.

For customers that found the suggested reviewers functionality useful, we recommend using Default reviewers and/or Code owners to facilitate automatic assignment of reviewers when a pull request is created.

Why we are making this change

Retiring the largely redundant Update page allows us to reduce the overall product surface area, and to focus on the core functionality and performance of the pull request experience.

[Marco van Rijst]

How can we set a forgotten remove branch on merge? the checkbox is nowhere to be found!

[Adam Cameron]

> Retiring the largely redundant [...]

Weasel words there.

So... not redundant then.

We regularly change the list of reviewers on a PR mid flight as it comes to light there are different areas of expertise needing to apply their attention. Or we open a PR with no reviewers as it's not ready for review, but we like to be able to easily see the progress of the diff. When ready the dev then adds the reviewers. This is a non-uncommon workflow I think.

We also semi-regularly need to create a PR between branch2 and branch1 whilst branch1's PR (into main) is being reviewed, so we can get visibility of the changes between branch1 and branch2. Once branch1 is complete and merged, we switch the branch2 pull req to point at main.

Also as the previous commenter points out, we often need to back in and check the "get rid" checkbox on a PR when the original creator forgot to do it.

Can't do any of that any more, can I?

If one can create something in a web UI, one ought to be able to edit it, until the object is "closed" (merged in this case). That's just fundamental UX, I think. Not least of all because it's been the UX here in Bitbucket for as long as I can remember.

> and performance of the pull request experience.

Doing a half-arsed job faster is not an improvement. The experience here has degraded.

Not your finest hour here, Atlassian.

[carlos_ijalba]

Not very nice this change, before if I did a mistake in a PR, then I could edit and change the branch origin/destination, now I have to cancel and re-create it, leaving useless garbage behind...