Try out the new Bitbucket Cloud pull request experience today!

[Tyler T]

@Ed Lomonaco , you can! Here is the documentation: https://confluence.atlassian.com/bitbucket/exclude-files-from-pull-request-diffs-961252751.html

The Excluded files filter is only available in the new pull request experience, and only repository administrators can add files to be excluded from the diff view.

[Ed Lomonaco]

be nice if you could hide the diffs for lock files, github does that and PRs are a lot easier to go through since you don't generally care about those files and their like 1000s of lines big.

[brahmana]

Been using this new UI for some time now and yesterday I faced a major roadblock which forced me to go back to the old UI for one PR.

When a PR is going through more than 2 rounds of review I use the `Activity` tab to look at all the comments from my last review session. For this I look at the commit from the author before my last review session and then I walk up the page till the latest commit.

While the same thing is possible in the "Activity" sidebar of the new UI, unfortunately, it does not actually show the entire comment text with the code context. The "Activity" window only has links, clicking on which the "Previous Comments" pop-up comes up show ALL the previous comments. In that pop-up I do not know which of the previous comments are actually from the last review session only.

I will have to explicitly look at the timestamps of those comments to see which session it very likely was. That is very tedious. The old "Activity" tab gives a complete chronological view of the activities and makes it very easy to focus on the changes in the most recent session.

Further if the comment was on a line which got deleted in a subsequent commit, new UI can't show any code context for that. The old "Activity" shows it. That is very helpful and very much needed.

Please bring both functionality back.

[Alastair Wilkes]

Thanks for the feedback -- we're planning to add a confirmation to the delete button.

[Alastair Wilkes]

We need to improve the "Former user" text, but we don't plan to display the avatar and name of the author on deleted comments.

[Alastair Wilkes]

Thanks for the feedback, Jon. We'll take another look at this.

[Alastair Wilkes]

Hi Maxim,

Thanks for reporting that. It's a bug; we'll get it fixed.

Alastair

[Jiri Hana]

The nice thing is that it also brought the simple editor back - it is so much easier to use than the new wysiwyg one...

[Alastair Wilkes]

Hi y'all,

We're working on some other improvements right now, but tasks are close to the top of the backlog. Stay tuned.

The ability to resolve comments is a great idea that we're considering for the future.

Thanks,

Alastair

[Alastair Wilkes]

Hi Jon,

Thanks for your feedback! Remembering this setting across page refreshes is in our backlog.

Alastair

[Alastair Wilkes]

Hi @Tjerk W, if excluded files isn't working for you, give our support team a shout so we can take a look: https://support.atlassian.com/bitbucket-cloud. Thanks!

[Francois Stephany]

We're developing tools to integrate with Bitbucket and would love to extend the new PR experience.

Do you know when external integrations will be enabled?

Will it use the org.bitbucket.pullrequest.overview.informationPanel location property of a webpanel?

[Jon]

I see the Activity card is out now.  :)  Looks great.

@Alastair Wilkes is there any chance it could be updated as events happen on the page?  Right now I have to refresh the page for it to show (for example) comments I've added since the page loaded.

This is probably a nice-to-have and not critical for sitewide rollout, but it would be very handy.

[brahmana]

Hi Alastair,

Thanks for the follow up. I wasn't aware of pull request tasks until another person commented about it on this same post. I will try it out, although going back to the old UI will now be some effort after getting used to the new one.

Really looking forward to the other planned workflow related improvements getting implemented.

Good luck to you guys.. :-)

[Joao Squillace Teixeira]

Thanks for getting back to my question! Definitely tasks and likes are on top of my team's need. I will wait for it :)

[Joao Squillace Teixeira]

Wondering if there is an ETA to have the new pull request experience with most of the old PR version features?

[Chris Morse]

@Manish Maharjan On a Mac there are 2 ways to get "Home":

• Fn + left and right arrow keys. Press the Function key and the right arrow key to jump to the end of a page (End), and Function and left arrow to jump to the top of a page (Home).
• Command + up and down arrow keys to go to Home & End respectively. 

[Alastair Wilkes]

Hi Gavriil,

Right now, we're working on adding back existing features and improving performance, so we haven't added this new feature yet. But it is planned!

Thanks
Alastair

[gavriil]

Hello,

Any updates on this issue?

Thanks,
Gavriil Tzortzakis

[sgautrin]

That said, adding special support for force pushes is not in scope for this redesign, but we may consider it for the future.

That's unfortunate. Force push is an inherent part of a widely used workflow, and there's good support for it in both gitlab and azure devops (don't know about github). Redesigning the PR experience and not using the occasion to at least catch up to the competition is not very wise imho.

[sgautrin]

As long as we are discussing the editor, I thought it'd be worthwhile to link to the issue that has been declared on bitbucket in hope of being able to keep being able to use the old markdown editor: https://bitbucket.org/site/master/issues/14468/

This issue has unfortunately been closed as “won't fix” so far; let's hope this change or we get an editor that is actually properly usable by technical people instead of only be usable by “button clickers”.

[Tim Creasy]

I haven't tried the new UI yet (I'm on Server).

But I'd like to request that it be possible to do a full-file code review (i.e. enabling a new reviewer to see and comment on all the lines of the files under review, not just diff excerpts with a few lines of surrounding context).

If there's an easy way to set up a complete review like this in the existing BitBucket Server pull request flow (maybe using a new branch/fork/repo?) I'd love to know!

[sgautrin]

I'm curious about that as well. Pull requests are mostly used by technical people (essentially developers though I guess other people might use them too, except it makes sense mostly for code, even if it's documentation as code).

And developers seem to me to be a population you do not want a wysiwyg editor for, and which should not have any problem with markdown.

The wysiwyg infuriates me as well. I could understand on jira or for the issued part on bitbucket considering it's used more by non technical people (but even then I really hate it), but for pull requests it really is for me an anti-feature. 

[J]

@Alastair Wilkes 

A couple questions:

- what's the best way to stay updated on when features land for the new experience?

- can you tell us which of the planned features will for sure land before general rollout and which will land after that point?

[Martin Ulmschneider]

Diffs would be nice, but more important to me are that comments stay visible (be it on the commit or the pr level).

I like how github does this: https://github.com/mulmschneider/playground/pull/1

Note how the comment is still visible on the Conversation tab, but marked as outdated.