Issue Summary

When a merge queue build fails and Bitbucket removes the pull request from the merge queue, the pull request activity log posts an entry linking to the pull request's Builds page. The failed merge queue build is never listed on that page.

A merge queue build runs against the temporary merge queue branch (for example merge-queue-1-2), not against the pull request's source branch, so it is not a pull request build and the PR Builds page cannot display it. The link in the activity log therefore always leads to a page that does not contain the build the user is looking for.

Steps to Reproduce

1. Configure a repository with a merge queue and a required build merge check.
2. Open a pull request and let the pull request build pass.
3. Add the pull request to the merge queue.
4. Allow Bitbucket to create the temporary merge queue branch (for example merge-queue-1-2).
5. Cause the merge queue build for that branch to fail, for example by merging another pull request into the target branch in the meantime.
6. Wait for Bitbucket to remove the pull request from the merge queue and delete the temporary branch.
7. Open the pull request and locate the activity log entry: "Bitbucket removed the pull request from the merge queue: One or more required builds have failed: <BUILD_KEY>".
8. Follow the link in that activity log entry.

Expected Results

The link in the activity log leads the user to the failed merge queue build, so that the reason for the merge queue failure can be determined from within Bitbucket.

Actual Results

The link leads to the pull request's Builds page. The failed merge queue build is not listed there, and cannot be, because a merge queue build is not a pull request build. The user has no path from the pull request to the failed build and must search the CI tool manually.

Workaround

Locate the failed build manually in the CI tool by searching for the plan branch matching the temporary merge queue branch name shown in the pull request activity log (for example merge-queue-1-2).