JEMH - Using an external key to identify issue

Raymond Schnidrig July 11, 2013

Hi all,

Is it possible to set up JEMH to use an external key to identify issues to update?

The use case is that we are sending issues from our help desk system to JIRA. The external help desk system uses unique keys per issue. JIRA issue key can of course change.

We capture the issues in a default project and would like to fill a custom field with the external key.

We would then like to use this custom field to match issues on any further incoming mails.

Thanks in advance,

Mark

2 answers

1 accepted

0 votes
Answer accepted
Andy Brook [Plugin People]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 12, 2013

Hi Mark,

Yes it is. JEMH enables integration with third party issue systems via keys unique to those third party systems, such as BugzillaId, Fogbugs etc. It works by matching the 'id' with a regular expression, and doing a search in a custom field by that ID. If an open issue exists, the body content is used as a comment in full, otherwise an issue is created with body content as description.

When body content is structured, as can be the case from an automated system, it is possible to use field level regular expressions to map specific values to individual JIRA custom fields. As a bonus, JEMH has Aliases that allow essentially a dictionary translation from external 'values' to internal 'values', eg an external priority of 'really important' could be mapped to 'blocker'.

See the How To Use the Regexp Field Processor . Obviously this regep heavy so you'll need to know some regexp basics. JEMH has an integrated Regexp Tester to help out.

0 votes
Mark Miller July 14, 2013

Hi Andy,

Many thanks for the answer ... this sounds perfect.

regards,

Mark

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events