Issue Summary

When mentioning an issue key in pull request description, this is also triggering workflow triggers and transitioning issues. Sometimes the issues mentioned in the pull-request description are not the origin the work, but only vaguely related. For example, a pull request description of "Fix for potential NPE found after releasing TEST-123".

Steps to Reproduce

1. Apply a workflow trigger to any transition in a JSW project
2. Mention an issue key in pull request description in GitHub

Expected Results

The mention of an issue key in pull request description should only link Jira issues, but not trigger Jira issue transitions whenever workflow triggers are configured.

Actual Results

Whenever an issue key is added to a pull request description, it also triggers transition if workflow triggers are configured.

Workaround

Instead of using a proper issue key like `TEST-123` when referring to unrelated work, you can refer to it with another separator than `-`. As in, `TEST 123` instead of `TEST-123`.