Bitbucket Workflow Triggers - Prevent Workflow Triggers when Merging Entire Branches

[Lexi]

We have workflow triggers set up so that when a developr's pr for a single jira issue is targeted into a branch it triggers status changes. When we do branch merges in bitbucket once a branch has been closed back into devel (for example) we want to make sure that that branch merge does not trigger jira issue status transitions.

Right now, for example, if we have 2 branches 8.1 and 8.2 and we merge 8.1 into 8.2, opening that pull request to merge the entire 8.1 branch into 8.2 will trigger a status change on all of the jira issues that were originally merged into 8.1.

One of our previous devops members had a method to prevent this but we lost that documentation and I haven't been able to find it anywhere online.