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

BitBucket Automatic Merge Failure email notification



Recently I have been asked to configure an email notification to Teams when an Automatic Merge Failure occurs when using the Automatic Branch Merging feature of BitBucket. 

I have a done a lot of research and have not been able to find a solution that works.  

I explored the Webhook route but noticed that there was not an event type that matched "Automatic Merge Failure":

I found this old thread about Stash, which described that the cascading merge conflict email would only get sent to the person who created the PR - but our situation is similar to one person who replied who described using a headless service account to perform the PR and merge:

I briefly looked into PowerAutomate tool to try and detect the email / Teams notification via the Office 365 BitBucket Connector but it also did not a way to treat "Automatic Merge Failure" - only triggers for all Pull Requests - which is useful but has too much noise for our team to catch the important missed merge conflict notice when it occurs.

So our need is to detect when an "Automatic Merge Failure" and to send an email / Teams notification.  

If anyone has any ideas or thoughts, I would really appreciate it.  


Thanks for reading and thanks in advance!



1 answer

Not an answer, but apparently there already is a 9 year old feature request for this:

Even a duplicate:


I guess we're left to our own devices.  


Atlassian if you're listening: please review BSERV-3551 and prioritize it - there is a steady stream of folks adding comments and requesting.  



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events