Alastair Wilkes Atlassian Team

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

Hi Martin, Thanks for your question. At this time, we don't support choosing which country your code is hosted in. Are you asking out of personal preference, or does this block your team from using Bitbucket Cloud? Let us know! Thanks, Alastair

Hi Steven, Thanks for your question. even a fully scoped app password doesn't work either That's very odd; app passwords are intended for that purpose, so if they're not working, that's a problem! It might be good to open a support ticket with the exact calls (passwords redacted, of course) you're making so we can take a…

Hi Kyrylo, Right now syntax highlighting only works in code blocks in comments and PR descriptions. We haven't added syntax highlighting to the actual diffs yet, but we plan to. Are you seeing this issue in comments or descriptions? Alastair

Hi Niall, It's not possible right now, but we plan to remove that limit in an upcoming update. Thanks! Alastair

Hi Sébastien, Thanks for the feedback. We will definitely continue to iterate on the activity feed before rolling out to all customers; what you see now is not the finished version. That said, adding special support for force pushes is not in scope for this redesign, but we may consider it for the future. Thanks, Alastair

Thank you all for trying out the new UI and for all the feedback! It's very helpful in prioritizing our backlog. I wanted to provide a quick update on some improvements we've recently made to the new pull request experience: * We've made lots of changes to improve rendering speed and scrolling performance * Error handling…

Thanks for the feedback, Nick! We're planning to add that improvement.

Ah, I see you replied to my comment on the public issue. Let's continue the discussion there, if that's OK!

Yes, that feedback is from developers writing comments in Bitbucket :) While I can't share more specific details about customer feedback or statistics, I do agree that the use case for Bitbucket is indeed a bit different, and we need to make sure it's a great experience for developers (especially being able to create…

Hi y'all, Thanks for the comments. It's clear that this is an important topic, and please know that we are listening and read every comment. As to why we're invested in the new editor experience, the "what has changed and why?" section here is a good primer on that. In particular, we're excited about enabling rich content…

Hi Tim, Thanks for the feedback! While it is possible to view and comment on every line (including context lines) in Bitbucket Cloud, you can't easily expand the whole file for viewing and commenting -- you have to manually expand context between diff hunks. We're looking at improving that in the future. On the Bitbucket…

Thanks for the feedback, Dan! We are working on adding the ability to exclude certain files and paths. Stay tuned.

Yep! Definitely. Those features are all the top of the list.

Hi there, Thanks for the questions! At present, there isn't a great way to stay up to date on improvements. As we ship missing features, we're updating the documentation and replying to comments here where applicable. We will need to revisit this when we prepare to roll out the new experience as the default option in the…

Thanks for the tip Sébastien, we'll investigate this case.

Thanks for the additional feedback, Jonathan! We do plan to implement the code context (diff) in the new UI like it was in the old UI. I like the idea of adding a button in the gutter. Deciding exactly which line that button should go on, however, is a bit tricky, since the line contents could have totally changed or moved…

FYI, this feature is now available! Click the "three dot" menu on any file diff to reveal this option.

We're not particularly focused on that right now -- but I'd love to hear what you'd like to see!

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.

Hi David! The first merge button is still present (we haven't implemented logic to hide/disable it when merging will fail), but if you actually attempt a merge when there are conflicts or failing merge check items, you will get an error and the merge will not succeed. We are working on bringing this more in line with the…

Glad you like it!

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!

Hi Steve, It's not there yet - we're working on adding a pared-down activity feed to the sidebar soon. You can check out all the other existing features we plan to bring back here (under What's missing?): https://confluence.atlassian.com/bitbucket/try-the-new-pull-request-experience-in-bitbucket-958455255.html Thanks for…

Yes, we plan to add that in the not-so-distant future. Thanks!

This feature is now available. Thanks!

Good news! This feature is now available. Click the "(N) prior comments" button at the top of each diff to view comments on lines that have been edited since the comment was made.

Thanks for the feedback. FYI, the new editor supports almost all Markdown (including `xyz` for inline code).

Hi Pavel, thanks for the feedback! This feature is noted in the documentation and will be returning soon. We appreciate you letting us know this feature is important to you!

@Hervé Le Meurthanks for the feedback, we're sorry the initial release has disappointed you. Obviously critical bugs are not acceptable and must be dealt with immediately. When it comes to deciding which features to include in a beta release (like the inline diff), it's definitely a tricky balance. For each existing…