When we build a job in Jenkins, sometimes the configuration varies by branch (e.g., dev vs. prod). This means that a given commit might succeed for develop, but fail for a feature branch. Unfortunately, currently Bitbucket only lets Jenkins notify for a commit hash, so it erroneously concludes that both develop and the feature branch are broken. Worse, the merge gate prevents develop from being merged to master due to this failed build.

Instead, I would suggest allowing the notification to specify both the commit hash and the branch. This is preferable over using the PR id (BSERV-11597) since you can always trigger a build without there being a PR at that point.