Automatic merge failure opens a PR but does not add the default reviewers. Please help.

[Debayan Majumdar]

Our merge happens through a service account user. The PR that gets generated if cascading merge fails gets opened under the service account and no one gets notified.

It also does not seem to obey the default reviewers rules. I have rules set up to add default reviewers for certain branches, but when PR is opened under the service account user after auto-merge failure, the default reviewers do not get added. Need immediate help with this. You response will be greatly appreciated.

[VICTOR-OSEGHALE]

Hi Debayan,

Thanks for reaching out here.

Can you add the logs generated when this occurs ?, this should give us a clearer insight of this behavior.

Kind Regards,
Victor - Application Support Engineer.

[foo Lizenzaccount]

We have the same issue. I guess it's just not implemented and therefore the logs won't help.

Can you tell use the expected behaviour of bitbucket?