/
Issue Association

Issue Association

Owned by Mike Harrison
Mar 25, 2025
2 min read

Issue association allows incoming emails to be matched against an existing Jira issue, allowing comments and other issue update events to be performed against the issue.

Evaluation order

Issue association strategies are evaluated in the following order:

  1. Issue key Directive. For example, @issueKey=ABC_123

  2. Issue key/custom field comparison Directive. For example, @issueKey=someCustomField=EXT_ABC

  3. JQL issue key Directive. For example, @issueKey=JQLStatement

  4. Foreign key association via regexp match, or first capture group. For example, ([A-Z]{12})

  5. Issue key in subject. For example, Re: ABC-123

  6. Original Message ID to issue association. For example, References: ORIGINAL_MESSAGE_ID

  7. Threading values in headers. For example, In-Reply-To/References: <JEMHCloud.ENV.ISSUE_KEY@HOST_URL>

Issue Keys In Subject

When enabled, JEMH Cloud will look for valid issue keys found in the incoming email subject.

Subject Issue Key Regex

The regex provided will be used when searching for issue keys in the incoming email subject. Only applicable if ‘Issue Keys In Subject’ is enabled.

 

Email Threading

JEMHCloud can check the References and In-Reply-To header value(s) for a Message-Id that matches an existing issue. The found issue (if applicable) will be used as the associated issue when processing the incoming email.

Use References Header

When enabled, email threading will be attempted by checking the References header of the incoming email. Only applicable if Email Threading is enabled.

Use In-Reply-To Header

When enabled, email threading will be attempted by checking the In-Reply-To header of the incoming email. Only applicable if Email Threading is enabled.

 

Associate Issue by foreign key

Issues can also be associated by a foreign key value. When enabled, any matching foreign keys in the incoming email will be used to find a matching issue.

Sender Regexes

The provided values are used to enable foreign key associations. If one of the comma separated values (E.g. sender1@company.com, sender2@company.com) matches against the sender of an incoming email, JEMH Cloud will attempt foreign key association.

Foreign Key Source

The location used to search for foreign keys in the incoming emails. Available options are:

  • Subject - Looks for foreign keys in the email Subject.

  • Body - Looks for foreign keys in the email Body.

Foreign Key Regex

The regular expression used to locate a foreign key from the incoming email. (E.g. (ABC+[0-9]+) to extract the value ‘ABC123’)

Issue Status

The selected statuses will be used to filter searched issues that match a found foreign key.

If left blank, any non-resolved issues will be searched.

If ‘Any status’ is enabled, all issues will be searched for matching foreign keys.

Foreign Key Field

The field selected will be the chosen field JEMH Cloud looks at when finding matching foreign keys on existing issues.