Try out the new Bitbucket Cloud pull request experience today!

[Jon]

There's still not a confirm for delete (at least on some outdated comments I just tried it on).  To make it worse, there's no visual indicator that the ajax request to delete the comment has been initiated, so I tried to click it again, but it updated the UI just before I clicked so I ended up clicking the Delete link for the next comment (which I didn't actually intend to delete).  

It reminds me of an LMS that once had a Delete All Users button right next to a very commonly used button in the admin UI.  Less fun. 

[Jon]

Now that tasks are implemented, I can add one to the initial comment in a thread and check/uncheck it depending on whether it's been fully addressed. This is nice, but what is really needed is a way to toggle the comment thread as resolved without having to manually create a task just for this purpose.  It also will keep the actual list of tasks from getting cluttered with these workaround "tasks".

If you find there's not much call for such a feature (maybe there is but task support is "good enough" that people are getting by?) I'm ok hacking together another chrome extension that can operate on the new experience. :)  But I think lots of people would love it.

[Jon]

update: there now is a link icon that jumps you to the task itself.  woot! thanks

[niallmuldoon]

Have just gone to do my second PR with the new single file system and hitting a new bug.

It''s showing empty diffs when there are real (non-whitespace) diffs.

I have sent you guys a screenshot of the actual diff and the PR showing the empty diff via the feedback. Hopefully you can get this fixed soon as it's another major blocker.

I am also being forced into the single file system due to the size of my PR (it's 121 files, half again are just Unity's meta files)

Edit: Just tried using the Legacy PR System to view the same PR and that is also showing me there are no diffs on files that 100% do have diffs. So it seems to be a bigger problem as it's hitting more than just the new PR Experience or viewing single files.

Drilling into the commits does show the diff for the files correctly. I have also checked all subsequent commits in the branch to check for any of these file's changes being undone and haven't found anything.

[Jon]

I think I remember seeing somewhere that the "who's viewing this" feature wasn't something they planned on bringing to the new UI (though that may be faulty memory on my part, or may have changed). 

You bring up a good point though.  It did also have the benefit of having a live view of new comments. If I remember correctly from the last time I tried the new UI (several months ago) the activity cart on the sidebar wasn't live and you'd have to refresh the page to see new activity.  If this is the case, there's a lot more being lost than just who's currently viewing the PR.  I agree about the usefulness of clicking the comments to scroll to them.  That is buggy in the old UI (sometimes it magically kicks you over to the Activity tab), but very useful when it worked.

edit: it looks like the activity is updating real-time now.  woot!

[Jon]

I'm guessing this is a bug.  I can't imagine BB would say "we can't help you - use a different product".  I've created PRs for branches that have a fair number of files.

I agree w/ being able to handle arbitrary sizes and load things a bit at a time.  Otherwise BB wouldn't be suitable for business use.

[kaushal.singh]

In Old UI, It shows who is viewing the PR which I didn't found in the New UI. Also if the person view comments something, it comes as a small notification on the icon of the current viewing person, which on clicking scrolls to the comment directly. This is a very useful feature especially when the PR is too long. Is it going to be brought to the New UI?

[niallmuldoon]

Hi,

I just tried to create a PR for a branch and am being told:

The PR only has 186 changed files. I am working on a small Unity project so half of those files are meta files.

The command it asks me to run... it's really not a very useful or user friendly way of doing things.

If you can't commit to being able to load PRs of an arbitrary size in one go then I would suggest a Load More button or a paginated approach.

This is huge blocker.

Thanks,

Niall

[Eugene Husak]

Hello!

I liked the new ui, and started getting used to it.
All was good, till today.

Seems like, you've rolled out this change:

Single-file-mode for Big PRs

And now, i have only one file visible on the page with message

To view another file, use the file tree in the right sidebar or navigational buttons in the header. 

Personally i found this as a big disappointment, cause it is very hard for me to navigate through the code changes when i need to manually click on each file

Can you add an option to disable that, please?
So the view will be as previous, all files on one page
you don't need to load all of them, they all can be collapsed
and then if i want to expand them - i will just click
and if diff is too big - you functionality you have already

Maybe i am missing something
Looking forward to your answer, thanks!

[Collin Peters]

The new PR experience doesn't handle tables as well as the old. The new tables all have columns that are equal width, rather than adjusting the widths according to the content. The results in a rather bad look when you have a lot of text in just one column and just a word or two in another.

[Manish Maharjan]

Hi @Alastair Wilkes , 

Has there been any progress on these issues or are these even in a roadmap? After almost a year, seems like these mentioned issues are still same. 

Would it be too much work to reduce at least unneeded space from the new pull request and making the full path visible?  As you can see from above left screenshot that if there is a file path like, 

Firstpath/Secondpath/Thirdpath/Fourthpath/Finalpath.php

then it creates space like 

Firstpath  /  Secondpath  /  Thirdpath  /  Fourthpath  /  Finalpath.php

 Was there any good reason for this? If not, any possibility to make this minor UI changes so that full path would be visible easily? 

Also, really looking forward to have list of File changed feature from old Pull request. 

Thank you 

[Matt d'Entremont]

We finally have approval to switch to a different platform, good luck all!

[Matteo Ferrando]

Merge checks don't specify why they are not passing. This makes me go back to the old experience.

[Dawid Konczak]

New feature lacks possibility to view if somebody is looking at your pull request. The old version had it and it was very helpful.

[Matt d'Entremont]

@Alastair WilkesAny chance syntax highlighting is going to appear anytime soon? GitHub has had it since at least 2011, it's hard to believe this feature isn't supported by a platform primarily used for hosting/reviewing code.

[djb]

The new experience pops up a message telling me that the PR has been updated; it includes a link to refresh the page. I refresh using that link and then a few seconds later, I get the same popup, but nothing has changed. There is no new Activity, and the build result has not changed. This has happened on many PRs - usually it is a relatively new PR, but sometimes it is after a reviewer comment or approval or new commit. It's a little annoying, so I just click the (x) close icon on the popup.

[Jon]

Love that this is progressing.

I'm seeing a Tasks card on the right-hand side now which lists existing tasks.  However, in the old experience the tasks were attached to comments.  In the new experience, those tasks no longer show up attached to the comments they were added to, so all I see is a list of tasks, each with text like:

• Done
• Done
• Done
• Fixed
• keep this
• Done

Out of context, the tasks are not much use.  Will "as they work on the old PR experience in 1.5 weeks" include this association between tasks and the comments they belong to?

Related question: will task creation and completion be events that show up in the Activity feed?  That could be handy (though if it's so much extra clutter, perhaps a toggle to include/exclude these in the feed would be handy; for that matter toggles for all the types of events in the activity feed would be nice).

[jarredc]

Coming soon!

[jarredc]

This is near the top of our list!

[jarredc]

Hey @sgautrin 

Sorry to hear that you're still feeling like this new experience is trailing the old one. We're working hard, and as the PM taking over from @Alastair Wilkes , I'm constantly reviewing our feedback channels to prioritize what will have the biggest impact. 

We're going to be finishing the Tasks functionality in the next two weeks so that tasks can continue to be associated with specific comments.  Our team's priority for the next dev cycle is ongoing usability improvements to existing functionality, launching 'Request's Changes' as a reviewer status, and before long, syntax highlighting. 

We'd like to move to resolvable comments before long, but it will involve some other dependencies being completed first.

Feel free to email me directly if you have any more feedback you want to share, jcolli2@atlassian.com.

Cheers,

Jarred

[djb]

The build status panel at the top right has a "refresh" icon,

but this does not refresh the build status; clicking anywhere in the  box simple expands/collapses the build status details. This is annoying when

1. The build is still running when I open the page

2. The build failed and then I update the PR externally and a new build gets triggered; this status line is obsolete and does not reflect the most recent build.

Please allow clicking on the recycle icon to refresh the build status without having to refresh the entire page. If that is not possible, use something that just indicates "build" (such as a Jenkins or other CI tool logo that is being used) or just remove the misleading refresh icon.

[Christof Wollenhaupt]

Thank you!

This is counterintuitive, especially as the position moved from left of the line numbers to right of the line numbers. We also lose the ability to move a comment plus there are now dialogboxes that appear at the top area of the screen.

[Deleted user]

The click area is much much smaller in the new version ! Try hovering on the vertical line.

[sgautrin]

Well, as time passes, I'm feeling more and more frustrated every day with the new PR experience and the lack of meaningful evolution to it.

* still no tasks support (huge regression) -- edit: just noticed it has been added, although with a UX even worse than in the old experience; indeed, in the old experience, you could select text from your comment before clicking “create task” and it would create the task with the selected text, and this does not work in the new experience; additionally, as tasks were previously created from a comment, they would have context, now in the new experience it does not seem to be the case (I have not tested it yet though, will do in the following days)

* still no resolvable comment chain support (which should have been the feature years ago instead of tasks in the first place)

* still no proper activity view: I frequently have to go back to old experience's activity tab to actually see what happened, and get a quick view of previous comments to see if they have actually been adressed and if so if they have been adressed properly (well, even to see if there's been an answer without having to go lookup in my mail notifications) - huge regression as well

And then, still no proper support for “PR versions”, i.e. being able to see what changed (commits, diff) between two specific updates.

Before the new PR experience beta a year ago, Bitbucket was already years behind any meaningful competitors, including the then VSTS from Microsoft (now Azure Devops), let alone older competitors like Github or Gitlab; and that's both feature wise AND UX wise.

Now, over a year after it came out in beta, the new PR experience manages to lag behind the old PR experience.

With you guys dropping the only thing you had that competitors did not have (mercurial support), it might be a good idea to try an catchup with your competitors feature-wise, instead of going backwards, don't you think?

[Christof Wollenhaupt]

I must be missing something very obvious: How do add a comment for a code line?

Atlassian has surely not removed the two single most relevant features that distinguishes a pull request in BitBucket from just discussing a pull request on Slack: Comments and Tasks?