Problem

When changes from forked(master) -> parent(master) are tried to merge with "Minimum successful builds" merge check fails and there are no for builds under the Commit and Overview tabs on the PR.

Environment

9.0.0+

Steps to Reproduce

1. Create a repository.
2. Enable merge check for a minimum of 1 successful build.
3. Fork the newly created repository in Bitbucket.
4. Create a plan in Bamboo for the forked repository.
5. Commit changes in the forked repository.
   Make sure this triggered the build in Bamboo and it's successful (shows up on the Bitbucket side).
6. Create a PR to merge changes from the forked repository to the parent repository.

Expected Results

Builds reflect correctly on the Commit and Overview tabs, satisfying the minimum build merge check and allowing us to merge the PR.

Actual Results

Builds don't reflect correctly on the Commit and Overview tabs, and the minimum build merge check fails, preventing us from merging the PR.

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available