Try out the new Bitbucket Cloud pull request experience today!

[Alastair Wilkes]

Yes, we will definitely bring back the activity feed before rolling out as the default option! It is a critical feature.

Our current plan is to add a new activity sidebar card. By "pared-down" I meant exactly what you wrote :) We'll ship a basic version and then make it better as time goes on.

[David Ménard]

The merge checks are not functional. It is even possible to merge with a conflict. 

[Mads K]

Glad to hear that! Other then that it looks like a great revamp!

[Alastair Wilkes]

We plan add syntax highlighting to the new view in time, but we need to bring some more existing features over to the new first. Thanks for the interest!

[Alastair Wilkes]

This feature is now available. Thanks!

[Jiri Hana]

Ok, I see. It would be even better if you made the wysiwyg editor optional. Unlike markdown, it is really cumbersome to use.  For example, I did not figure out how to insert inline code in this window (not code block). In markdown it is a simple `xyz`.

[Alastair Wilkes]

Thanks for the feedback, Mike!

You're right - interaction performance isn't where we want it to be yet, and we're working on it at the moment. I'm curious if using the ] keyboard shortcut is more performant for you?

Ability to know which files have been (re)viewed would be good. We have received similar feedback from several other customers, so we're definitely considering that. Thanks!

[Hervé Le Meur]

Also really appreciate the effort and improvements of the pull requests UI, but disapointed with this half-backed release, between the inline diff not present (which in itself is quite a regression), and the potential bug I've stumble uppon

For a service which main point is development and code management, I find it's odd it has been released in this state.

[Dan Cumings]

One of the features they are working on is making it so you can view comments even after a pull request is updated.  For now a good workaround is to make a synopsis of all the comments at the top of the pull request.

[haithem_mosbahi]

Looks great so far ! 

Do you have any plan to implement Pull Request Tasks in the design ? 

ah I just saw the what's missing section in the article.

Thank you and looking forward for more features 

[Jon]

The Give Feedback modal now seems to be working, so I've re-submitted the scrolling issues there.

I tried creating an issue at the jira link above, but it looks like it steers you eventually back to the Give Feedback features in the individual products and that creating issues in jira is only for Atlassian people (which is fine, though the Give Feedback seems to be less vendor-customer dialog friendly).

Can anyone on the BitBucket team who may be monitoring the comments on this post speak to whether this is still a channel of 2-way communication between the team and customers?  If no reply is given w/in a week or so, I think we can assume it's been quietly retired as such and to stick to the Give Feedback feature and hope those comments are seen.

[Jon]

Awesome - thank you

[Jon]

@Tyler T @Alastair Wilkes @jarredc 

Just wanted to check if these comments are still visited by/responded to by the Atlassian Team.  Usually the response here has been pretty good, but I haven't seen any replies to this issue.

I'm personally running into issues with the Give Feedback button in PRs (Details tab at the bottom).  When I click it, it shows a spinner for about a second, then it goes away.  I see no JS errors or network tab activity and have tried with all extensions disabled.  Without that, there's no way other than these comments to provide feedback that I'm aware of.

[Jon]

Bumping this, hopefully.

@jarredc or anyone at Atlassian - can you comment on this issue?  I've run into it occasionally (just now, in fact) and it's kind of a speed bump in the workflow whenever I do.  I can still get at the info I need if I switch over to git and start looking at file history, but it would sure make the UX better if we could expand the context like we used to be able to.

[Jon]

In the right hand column, at the bottom of the Details tab there is a "Give feedback" button.  When I click it, a spinner appears in the button for a second or two, then disappears.  Nothing else happens.  Hoping that posting here is still a way to communicate to the dev team.

[Jon]

@jarredc any update on the scrolling issue?  I really like the 3 tabs at the top, which helps some.  But on the Activity tab itself, once there are more comments than will fit in the viewport vertically (about 4 or 5 comments on my desktop monitor), this is still an issue.

Without a scroll indicator, there's no way to see where you are in the list, and without a draggable scrollbar, there's no way to quickly get to the top or bottom of a long list.

It seems the solution is pretty straightforward (UI wise, if not implementation wise).  The vertical scrollbar that's currently present applies only to the main portion of the screen, and should be proximate to it (to the right of it, immediately to the left of the tabbed details/files/activity column).  This would make place for a vertical scrollbar proximate to the tabbed column itself, and avoid two side-by-side vertical scrollbars (which is never good UI).

In fact, this is exactly how the Jira issue view works already: a vertical scrollbar for the main area, and one for the right-hand column. When either area is shorter than the viewport, the scrollbar for that area isn't present, which is appropriate.

This seems to be a pretty common UI design pattern when dealing with split views/panes - each has its own scrollbar on the right.

[Jon]

It looks like this has been fixed.  Thanks!

[Tyler T]

@James Brantly , work is starting on this soon. Please follow the public ticket to track the progress:

https://jira.atlassian.com/browse/BCLOUD-7968

[Jon]

@jarredc Any update on this regression?  Looking at an outdated comment with no ability to view more than an arbitrary and small amount of context can make it difficult to tell what the comment is about.  Bringing back the ellipses buttons on the left to load more context would be much appreciated.

[Jon]

@jarredc is bringing back this feature still on the table?

[Deleted user]

The new layout made the "merge" action hidden behind the ... button. This is a very bad UX experience, since the merge action is the single most important button on the page, and now it's hidden behind extra clicks. Please put the "merge" action back on top - even if that means the "request changes" button has to go.

[Tim Pommer Dybdahl]

The new exprience is a somewhat mixed bag. On one hand I like the new Details pane, and the Files pane is even half decent.

But the Activity pane unfortunately leaves a lot to be desired to a point where it is completely useless.

You can only see the latest reply on a comment, but the comment itself is not shown, meaning you have to click every single one of them to see what is being responded to. And this only works if the file is still part of the PR.

On top of that the "see whats changed" link next to approvals have now dissapeared, making it even harder to stay on top of what has changed since the last time you looked.

I like the fact that you are now able to mark that you have seen a PR but not approved it through the use of "Request Chagnes". But since you can't "see whats changed", it is pretty useless compared to just adding tasks to the PR.

[Nick St Pierre]

I have this same exact problem. The team I work on is constantly adding and editing large files and I can no longer leave in-line comments because the diff won't even load. I have to leave comments on the main comment section of the PR specifying the file and line number whenever I find any issues in a PR. To say this is a massive inconvenience is an understatement. How could this have been shipped with such a huge oversight?

[Nick St Pierre]

Do you plan on increasing the render size or somehow allowing users to define the upper limit? I am constantly adding/editing large files on my project and the new PR experience is practically unusable for me.

[J]

@jarredc is this issue something being considered?  I'm still experiencing it and would love to have it resolved if possible.