Issue Summary

When mentioning an work item key in pull request description, this is also triggering workflow triggers and transitioning issues. Sometimes the work item mentioned in the pull-request description is 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 Jira project
2. Mention an issue key in the pull request description in GitHub

Expected Results

There should be an option for users to choose if they want the mentioned issue key in the pull request description to

• Only link Jira issues,
• Or to also 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 a 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`.