What is JEMH?

• JEMH is an Enterprise mail handler for JIRA
• It is an advanced issue routing mechanism based on the domain
• JEMH is simple to configure and easy to use

Why JEMH used?

• JEMH used to route incoming emails to different projects based on domain, group or keyword
• Using JEMH, user can customize template notification sent to reporter (customer)
• JEMH supports several flavors of an email format that can be used to update all JIRA’s default custom fields, manipulate workflow, log work, etc
• In JEMH, a user can configure default target project, Issue type, Reporter, Summary, Assignee etc while profiling configuration. Be aware that different projects have different issue type schemes so a default issue type may not be always valid
• In JEMH, multiple incoming email id’s can be configured for multiple projects

JEMH Configuration

Install JEMH plugin from marketplace

• – https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui

Profile in JEMH-

• Profiles are top level containers for configuration
• When a JEMH inbound mail handler is configured, a Profile will be selected from a list
• Profile can route emails from one mailbox to multiple projects, thereby addressing a major scalability issue with the default mail handlers

• Creating default profile group- While creating profile group user have to provide Profile name, Group key, Default profile and Group order
• Default profile check box is used to nominate a current profile as default profile in the particular group
• A user can add multiple profiles in a single group
• It is as simple as creating a new profile, user need to give group key then click on submit button you’ll see the new profile added into the group structure
• After creating profile, associate that profile in JEMH email handler like this –JIRA Admin > System > Mail > Incoming Mail section
• Mail Handler entries are added to associate an Incoming Mail Server with a handler
• Going back to the JEMH Profile screen, the default profile is shown as associated, indicating the group is hooked up to a Mail Handler in JIRA

Profile configuration

• Table shows the configuration for the selected JEMH profile
• In that, user can map multiple projects and also able to set default issue fields for that project
• In project configuration, user can do incoming mail domain mapping per project
• Email configuration provides user to configure ‘Catch Email Address’ for an issue creation via email
• In Whitelist configuration user can configure Blacklist, Greylist and default email address or regular expression
• Blacklist – A blacklist is a collection of entities that are blocked from processing, where a user can provide an email address, subject or regular expression that needs to block.
• Greylist – It is a way to mark some content as bad based on regexp
• Ad-hoc Notification – Shown as an Issue Screen action button, JEMH AdHoc notifications allow users to send out canned responses or customized content to specific users, or users defined in JEMH email custom fields NOTE– Changes can take up to 5 minutes to apply due to caching/performance measures
• Template sets – Template Sets allow configuration of all JEMH injected text or notification content, providing Subject and Text/HTML content template editing as applicable. To be clear, JEMH Templates are not replacements for JIRA email templates
• Test cases – Test Cases allow rapid testing of an email content against configurations and completely bypasses inbound mail handlers, so a configuration can be validated before being hooked up to the outside world. A Test Case email is the native raw text email content that travels over the wire, not just content. Test Cases can be generated from Audit log information for problem diagnosis.
• Event Listener – Issue Events are monitored through Project Mappings, each Project Mapping has per-event Template Mappings as each Project can then have specific events enabled or not. Once created, a Project Template Mapping is shared between Non-JIRA and JIRA notification handlers, where DEFAULT is selected, this means the internal JIRA templates are used. The user can configure notifications for the non-JIRA customer.

Who uses JEMH

• JEMH is used by organizations having multiple customers
• Cost efficient than JSD (JIRA Service Desk)
• Provide better notification functionality than JSD (JIRA Service Desk)

License cost

• JEMH software licenses give you perpetual use of JEMH versions released within your maintenance window. Purchases include 12 months maintenance for updates and support, starting from the date of purchase. Renewing maintenance is entirely at your discretion, but guarantees latest JIRA release compatibility, more features etc.

Conclusion

JEMH provides the best way to route an incoming email to different projects and also provides customized notification template with minimum cost.

The post Intro and Configuration to JEMH Plugin appeared first on DevOpsTech Solutions.