Currently, the Jira Service Management (JSM) built-in mail handler automatically detects and associates issue keys found anywhere in the email subject or body, even when those keys are embedded within other words or attached to additional characters (e.g., "XYZJIRA-123", "JIRA-123ABC", or "JIRA-123:1223"). This can result in unintended comment associations and workflow disruptions.

Requested Enhancement:
Introduce a configuration option in the native JSM mail handler to restrict issue key detection to standalone keys only—i.e., keys that are separated by spaces or punctuation and not attached to other alphanumeric characters. This could be achieved by:

• Enforcing word boundary checks when parsing for issue keys.

• Allowing administrators to specify or enable regex-based matching for issue key detection.

• Providing a toggle or setting in the mail handler configuration UI to enable this stricter matching mode.

Example Scenarios:

• "JIRA-123" in the subject or body should be recognized and trigger comment association.

• "JIRA-123:1223", "XYZJIRA-123", or "JIRA-123ABC" should not trigger key detection or comment association.

Business Impact:
This enhancement would prevent incorrect issue associations, reduce manual cleanup, and improve workflow accuracy for organizations that rely on precise email-to-issue mapping.