Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Can we opt out of the new three-dot diff experience?

Is there a way for us to opt out of the new 3-dot diff experience? While I understand the change was done for performance reasons, it has Bitbucket unusable for us.

We rely on knowing that when we do a PR into a specific branch, we get the changes between the two branches to show up - not the changes between our feature branch and a common ancestor.

Setting up a PR of a feature branch into our develop branch but then showing changes that already exist in the develop branch is quite misleading.

We've never had any complaints about performance of diffs or PRs. If there was a slow diff because of lots of changes, that was totally acceptable to us because we knew there were lots of changes. We are happy to trade that performance hit for large, complex diffs if it means we'll get accurate diffs and PRs.

The "workaround" of pulling the destination branch into the feature branch does not work for us as there may be code in the destination branch that we do not want in the feature branch yet.

Thanks in advance.

2 answers

1 accepted

1 vote
Answer accepted

@Matt Pedersen and everyone, we aren't alone, I found the feature request. Vote for it here

We have the same question with the same reasoning as you, Matt, on all points.

Are we in the minority here? We use master to represent Production, and everyone branches off of that. Our PRs first need to go to staging, which is where these diffs are now broken. They still look right against master, but against staging we have any changes from other features that are already in master showing up again. And we certainly cannot merge down from staging into feature; that would prevent feature from going to master until everything in staging is ready--which is not our workflow. Features go one at a time. We don't do a release candidate or release branch.

We also found the performance acceptable as it was.

It would be great to have the option to use the prior diff style.

This is a very common workflow. It's also what our team uses, so these new diffs are total garbage.

Like # people like this

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events