The current situation with Stash is:

Build status are linked to commits.
We can set an option to prevent pull requests merge action if there is not enough builds and if any build fail.
A single commit could be included in many pull requests, targetting different branches.

Core issues are:

• Sometime, you look at the status of the pull request, and you see the status of the last commit of the pull request. So status could be confusing for a user who care only about builds relative to the specified pull request and not the results of all the builds.
• We you set the option to prevent merge if there is not enough valid builds, and all builds successful, this option could prevent merging because of the result of a build that is relative to the same commit but to a different pull request targetting a different branch for example.

What we need:
We need to have a clear and relevant status. Could Stash propose a build status that return only the builds results that are relevants for the context? AKA:

• If you look into a branch, status on the commit in the branch
• If you look specifically at a commit, all builds results
• if you look at a pull requests, only the builds that are relative to the concerned pull request

We need also to have a trustable merge button, that prevent you for merging only if the builds concerning the pull request in question are broken, and ignoring the results of non relevant builds.

Regards,
Pierre