64a00d9aa858 Not 100%, but strong chance the feature will be available in mid-April.

dparrish Thanks so much for the update. Much appreciated. Could you please clarify what you mean by ‘soon’? Are we looking at days, weeks, months, or longer?

Thanks all for your patience. We did have to pause the project based on other priorities, but it's up and running again and we'll have an update soon. I'm sorry that it's been such a long wait for this feature!

For anyone that does not want to wait, I created a userscript that you can install into the GreaseMonkey or TamperMonkey addons in Firefox and Chromium based browsers. If you already have the addon installed, go to https://greasyfork.org/en/scripts/492710-bitbucket-cloud-helper-functions to install or view the source on my GitHub

dparrish - I'll second Basin's comment -  We've been patiently waiting and MANY in my org would REALLY like this feature to get across the finish line.   

dparrish Just checking on the status as the last update was 5 months ago. Is there an ETA on when this feature would be available?

dparrish 🥲 i never thought this day would come

Hi all 👋 Well I know it's been a long time coming, so I'm happy to say that Bitbucket Cloud has started work on an option in repo settings (and project settings) that controls the default for "delete source branch after the PR is merged". We'll post an update here when the feature is available.

+1

9a412cca67c5 I am not sure anymore if this is just a bummer, if not a disgrace. This item was created 7 years ago. It was already implemented in Bitbucket Server. They moved us to cloud (as they discontinued a Server).

One would expect that most basic functionality would be eventually moved to the cloud. Especially those that are very highly rated and technical simple (at least should be) as this one.

An explanation from Atlassian product management would be appreciated, what are their thoughts on all this.