We've added support for the following additional merge strategies:

• Rebase + fast forward (BCLOUD-16610)
• Rebase + merge (BCLOUD-17881, BCLOUD-19186)
• Squash, fast forward only (BCLOUD-16338)

It's also now possible to sync a feature branch via rebase (BCLOUD-6202).

https://bitbucket.org/blog/branch-sync-merge-rebase

Please implement this! It shouldn't take that long, simply do:

git rebase ${DESTINATION_BRANCH}
[[ $? -ne 0 ]] git merge --ff-only

Can't be that hard right??

We're working on adding support for several additional merge strategies, including:

• Rebase + fast forward (BCLOUD-16610)
• Rebase + merge (BCLOUD-17881, BCLOUD-19186)
• Squash, fast forward only (BCLOUD-16338)

dgarcia@atlassian.com we'll be moving away from a commercial Bitbucket account to Github, in part because of this feature missing in Bitbucket.

Agreeing with all the comments below. Providing rebase merge features (with or without fast-forward), is essential for keeping a linear git history if you don't want to be be manually rebasing all day long.

Please work on this!

Hi, we just moved to Bitbucket Cloud, and this missing feature is very annoying ! 

Our developers have sometimes to wait for 30 minutes just to merge their PR because of this.

We need this back !

We have released a plugin for Bitbucket cloud that supports rebase strategy and other features.

Those things that gets released in two years are solely around pipelines, and one item on project level branch permissions.

Such a thin roadmap does not feel like being listened to, but mostly feels like Atlassian is exploiting its vendor lock-in. Especially when reading that apparently the featureset of the Cloud version goes down when migrating from Server.

@dgarcia Why was this feature (and so many others) that worked well in Bitbucket server removed/left out from the cloud version? Bitbucket Cloud feels like a purposefully feature-poor alternative to Bitbucket server, and this is just sad.

@dgarcia this is extremely disappointing. We have migrated one team to the cloud version of Bitbucket and put all other project migrations on hold.

So far the only upside to migrating any developers to cloud has been freeing up server licences. We've now got a dev chat channel dedicated to the pointless double handling required to avoid manual rebases all day long.

Will this functional regression between the server and cloud versions be fixed before support for server ends?