Background

When a pull request is added to a merge queue, Bitbucket runs a build against a temporary merge queue branch/commit (e.g. merge-queue-1-2), not the pull request's source branch. Because of this, merge queue builds are never treated as "pull request builds" and do not appear on the pull request's Builds tab.

As a result, users have no way to see merge queue build activity (running, successful, or failed) from the PR Builds tab. If a merge queue build fails and the PR is removed from the queue, the only trace of it is a single activity log entry - there's no ongoing visibility, and diagnosing the failure requires manually searching the CI tool for the temporary branch name.

Feature request

Extend the pull request Builds tab to also surface build statuses associated with any merge queue attempts for that PR (builds run against the temporary merge queue branch/commit), alongside the existing source-branch/PR builds already shown there.

Why This Matters

• Completeness of the Builds tab - Users expect the Builds tab to be the single place to check all CI activity relevant to a PR. Today, merge queue build attempts are invisible there entirely.
• Discoverability - Visibility into merge queue builds shouldn't depend on a user reading a specific activity log entry; it should be visible wherever they'd naturally look for build status.
• Faster failure diagnosis - Surfacing merge queue build status inline lets users see and act on failures without leaving Bitbucket or manually searching the CI tool.
• Consistency - Successful merge queue builds are also currently invisible in the UI; showing them (not just failures) gives users confidence the queue is progressing correctly.