Quickstart

This quickstart shows the bare minimum that needs to be done to get issues created in a project via JEMH.

Step 1 - Install

Search for and install JEMH through the Jira Universal Plugin Manager (see how).

Step 2 - Install an Evaluation license

Step 3 - Create a Profile

Step 4 - Update the profile configuration with a catch email address

A catch email address is an email address that your JEMH profile is configured to receive emails to (the address of the mailbox that JEMH is connected to). You should always specify a list of catch email addresses for mailbox address that you have configured JEMH to handle email from. JEMH automatically filters catch email addresses from email notifications so that you do not notify your own JEMH incoming mailbox of issue notifications, not specifying a catch email address can cause the JEMH mailbox to be notified of issue events that can then lead to a mail loop.

Step 5 - Update the profile configuration with a Default Reporter

The Default Reporter is used to create issues on behalf of users who either lack application access or the right to create issues, the Default Reporter is also the reporter for issues created by Non-Jira users. Fore more information about situations when the Default Reporter is used see: Create Issues (from Jira 7.0).

The Default Reporter will require issue permissions in the associated projects that your JEMH profile will be interacting with. 

Step 6 - Create a Default Project Mapping

JEMH Issue Creation is driven by Project Mapping's. A Project Mapping contains project specific JEMH configuration to be used when processing emails for the project defined in the Project Mapping. When processing an email JEMH will evaluate all Project Mappings defined in a profile to try and locate a Project Mapping with rules that match the email being processed. If a matching Project Mapping is found, an issue will be created in the project linked to the Project Mapping. If no Project Mapping matches via a rule, an issue will be created in the Default Project Mapping if one is defined. For this quick tutorial we are going to configure JEMH with a Default Project Mapping so that all incoming emails that do not result in an issue comment will result in issue creation inside the project defined in the Default Project Mapping.

Step 7 - Enable JEMH Auditing

JEMH Auditing is used to keep a record of all emails that are processed and will also has a Report that describes the processing that has occurred, allowing you to review if emails resulted in an unexpected outcome. For more info about auditing see: Use Auditing

Step 8 - Create and run a Test Case

Step 9 - Create an inbound mail handler

If you have yet to setup inbound email, do so now. Once an inbound mail configuration has been setup (files/POP/IMAP):

Read emails as read option can only be enabled when using IMAP as the connection protocol. If this is not enabled then Jira will delete the mails after they are processed. If enabled then Jira will only mark these as read, allowing the mailbox copy of the email to be kept.

Forward email?

Unlike Jira mail handlers, JEMH owns all functionality within the mail handler space, including error management and notification. A dummy value is provided to satisfy Jira error checking, to modify the 'forward' user, go to the JEMH Profile/Configuration/Notifications section. JEMH allows both users and static email addresses for forward notifications and there must be at least one user or email address for JEMH to process forward notifications.

Related Articles