Can't filter on Bitbucket PR source Branches instead of Target branches

[SumanDas94]

I have a requirement where i need to filter branches for a build based on the source branch of PR. Currently build is triggered anyways and have to write custom logic inside the jenkins script to handle the further build steps prevention on that branch as my filtering criteria needs to be the source branch and not destination branch Is there a reason why we use only destination branch for the plugin branch regex matches (for PRs) and not source branch ?

[DzmitrySurovets]

Are there any updates/comments?

[MohamedKHALILRouissi]

hello in case for git workflow with trunk based development , it's better to filter by source branch this will allow me to block builds at early stage and remove lot of parsing and if condition , basically we can have a single fullfilled event which equal to pull request merged that can handle action related to main branch , is it possible to change this behavior atleast for created_comment,created_pullrequest,updated_pullrequest , merged can keep the same behavior