...
About foreign key association
This method uses a regular expression to locate find data (a “foreign key”) in an email subject or body, and store that data in a selected field. Subsequent emails that have the same foreign key regexp match will then be associated with the email that has the foreign key stored. This method is useful when dealing with emails coming from an automated system such as Bugzilla.
...
This makes the necessary settings visible on screen:
Setting | Details |
|---|---|
Sender Regexes | A CSV capable field, where a list of email address regexps can be entered. If the sender address sender matches one of these regexps, JEMHC will try to associate the foreign key in email with the issue. |
Foreign Key Source | The location in the email where the foreign key is to be found. Choices are Subject or Body. |
Foreign Key Regexp | The regular expression used to extract the foreign key from the email. The first matching group (indicated with round brackets) is the returned value. |
Issue Status | When this field is used, only issues with the selected statuses are candidates for issue association. Leave this field blank to allow non-resolved issues only. |
Disable issue keys in subject | When active, standard issue key in subject association is disabled. |
Foreign Key Custom Field | The custom field to be used for storing the foreign key on an issue. |
For our example, we have the following configuration:
...
The results:
First email with new foreign key in body | Second email containing same foreign key in body |
|---|---|
 |  |
Whole subject matching
In this scenario, you do not have a specific key to match with in the email. Instead, you may choose to use the whole email subject as the matching key. Whilst this is possible, it is not a very strong issue association method as there is the possibility of two unrelated emails having the same subject. Therefore, issues could be wrongly associated when using Regexp Foreign Key Association in this manner.
...
When JEMHC processes an email, the emails message-ID is stored. If a subsequent email refers to the original message-ID in its In-Reply-To and References headers and if enabled sub option(s) are enabled i.e.In-Reply-To and References; then JEMHC will drive threading dependent on the related header(s) options are enabled then issue association will occur. Email Threading behaviour can be disabled or modified via Profile > Project Mapping > Pre-Processing > Issue Association > Email Threading.
Embedded Issue Key in Message ID
...
| Filter by label (Content by label) | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|