Atlassian bought Bitbucket after it was already mature. That's why!

Not quite. Bitbucket was acquired in 2011, only supported Mercurial and was missing a lot of features, including the pull request available today.

Perhaps they didn't fire the whole bitbucket team after buying them, so the people were still able to produce good software for a short time.

Bitbucket Server, which some people are referring to here, was build from the ground up, tailored to a self hosting environment.

I have a few plugins to improve the PR's in bitbucket too, showing you the relative size of the PR compared to others you normally work with.

Includes the language breakdown and such. Makes it much easier to know if you should be blocking out 5 mins to 5 hours to review something and if you even should be depending on the language.

Alas, Atlassian does not offer PVA for Bitbucket (it was meant to be there in July) so I cannot release it since it costs me money to host. I really wish they would invest more time into Bitbucket.

Try to use Intellij's Github plugin. It does wonders.

We use bitbucket cloud, and the PR UX is awful. Which version are you using? Are you using a browser extension or something? Compared to UpSource or GitHub, Bitbucket PRs are very rough.

Bitbucket Cloud and Bitbucket On-prem are two entirely separate products. It makes about as much sense as you can expect from Atlassian. The former was a Mercurial thing that they purchased then later removed Mercurial support. The latter used to be called Stash.

We moved from Bitbucket On-prem to Gitlab and I must admit I do miss parts of Bitbucket's UI. It was much easier to find reviews you needed to do and it was much clearer when reviewers had finished reviewing and if work needed to be done. Gitlab should just copy this stuff.

I was the head of product for the developer tools at Atlassian in 2012. We thought long and hard about taking Bitbucket cloud and packaging it in a VM (which is what GitHub did at the time) or leveraging the platforms we’ve already built for Confluence and Jira that would give us access control and a plug-in system from day 1. It was a tough call.

Ultimately we’ve decided to build on top of our server platforms and target companies with 1000+ employees from day one. That decision had a huge impact on how we approached performance and what features we prioritised. The hierarchy of projects and permissions associated with them as well as the way we designed Pull Requests are good examples of that.

It was the right decision at the time, even if the product happened to be different in cloud and server, which did lead to some confusion. But Stash customers were really happy with the product.

bitbucket PR is horrible compared to reviewboard