automatic merge of pull requests doesn't work in certain user cases where source branch commit is associated with multiple build results

Issue Summary

automatic merge of pull requests functionality doesn't work in certain user cases where the source branch commit is associated with multiple build results.

Steps to Reproduce

1. Create a pull request.
2. Ensure that the following branch restrictions are enabled for the pull request destination branch pattern:

• • At least 1 build must pass.
  • No builds are in progress.
  • No builds have failed.

       3. Execute two builds for the source branch commit. One using Bitbucket Pipelines and the other from a third-party CI build.

       4. To test this scenario, ensure that you complete (with successful status) one of the builds as soon as possible (either the one from Pipelines or the one from the third-party CI).

       5. While one of the builds has been completed successfully and the other is still in progress, click on the merge button. This action will open the merge window.

Expected Results

In the merge window, you should be able to see the automatic merge button, represented by a blue merge button along with a clock symbol, indicating that a build is in progress for auto-merging.

Actual Results

However, the merge button itself will appear grayed out, accompanied by a message stating "1 merge check has not passed."

Workaround

Currently, there is no known workaround for this behavior. One needs to wait until the build is successful if the source branch commit is linked with multiple build results.