Bitbucket Closes a Branch Even Though the Merge Failed Due to Conflicts

[sholsinger]

I just lost two issue branches on bitbucket because I was trying to merge them. I checked the 'close after merging' checkbox intending to close them after they were merged. Unfortunately the merge failed and they were 'closed' anyway.

Steps to reproduce:

1. Create a branch with a commit that conflicts with master.
2. Attempt to merge the branch with master via Bitbucket's web UI. (Ensure you select the "Close source branch" checkbox)
3. The merge will fail and you'll be alerted.
4. Click the browser's back button and you'll see a 404 message because the branch was closed.

[Gary]

Hi Stephen,

Yes - this is a bug reported at https://bitbucket.org/site/master/issues/10242/unintentional-branch-deletions-from-merge.

Cheers,
Gary 

[Seth]

This sounds to me like a genuine bug, which should be reported at jira.atlassian.com