Is it possible to restrict a build notification to a single issue key?

[jgmsb]

Describe your use-case which is not covered by existing documentation.

Hello,

I wanted to ask if the option to notify only one issue key above all the issue keys from the branch commits exists. I am experiencing cross build notifications between Jira Issues when merges between branches are done and commits with different issues keys are being inherited, in my case from the develop branch. The case is:

1. I create and develop new feature branch, build is ok and green check is marked in my XXX-123.
2. I merge to develop.
3. One college merges develop into his feature branch (inheriting my issue key in commits). His build fails (not because the merge or inherited commits), and the failed build notification is send to my Issue XXX-123 (which is merged and done) and his XXX-456.

I've been searching in the documentation and the code for an option preventing this (something like restrict the build notification to a single hardcoded issue key), but doesn't seem to exists. Or maybe I'm missing something. I wanted to confirm it anyway.

Thank you very much in advance!

Reference any relevant documentation, other materials or issues/pull requests that can be used for inspiration.

No response

[luqq]

We need this case to be implemented so our organization can integrate release process in Jira. Could you guys please take a look at this? Thank you in advance.