Problem Definition

Currently, JiraXXXXEvents will fire whenever something that matches what looks like a Jira issue key is mentioned. Whether it be in a pull request, commit, etc.

The problem arises when work is done and resolved on Jira issues and commits and then a PR is opened.

Tickets that were previously closed can be reopened through automation if commits mention those issue keys in the commits that will be merged in a newly created PR.

Example

1. Create Jira issues to track work needed to be done.
2. Commit code with commit messages that mention those issues.
3. Work is resolved and issues are closed.
4. Open a pull request to merge those changes to the main branch
5. All previously close issues reopen due to the commit messages in the commit list for the pull request
6. Issues are subsequently reclosed when the PR is merged

Possible solution

Have the ability to configure the webhooks to not send a hook for the commits listed in the PR, but only issues mentioned in the PR title itself. Or have the ability to specify how Jira processes events (i.e ignoring commits messages in PRs).

Workaround

Plugins such as ScriptRunner may have a solution that allows you to specify what events can trigger specific automation in Jira.