JEMH is an enterprise level mail automation tool for Jira covering both inbound mail processing as well as outbound notifications. There are so many features its hard to cover what matters to the customer:
JEMH as a mail handling solution is available for Jira Server and DataCenter, we also have a Cloud variant offering a subset of the features here (notably no script support yet).
Inbound
fully support core/software and JSD (portal) projects
scale inbound mail handling through “Rule” based “Project Mapping” e.g. map mail (TO or FROM) a given address, customise an issues creation at the Rule or Mapping level. Jira itself will not scale beyond 80-100 physical mailbox-handlers, JEMH can reduce N mailbox polls into 1.
comprehensive image blacklisting features to stop ‘icon spam’ from being added to Jira
mail blacklisting by subject (no more OOO notifications or delivery status failures)
very flexible reply-to filtering support to keep issue content clean
“Auditing” support to track what happened to mails, and “Test Case” features to allow mails that were not processed as required, to be investigated more closely.
dynamic resolution of email format problems on the fly, where email headers contain illegal values (that Jira std would be unable to process), JEMH can operate on the mail to fix syntax issues uncovered over the many years JEMH has been a leading solution!
JEMH Profile configuration export/import, enabling ‘vairiants’ of configuration to be used as well as core-configuration transfer between environments (DEV>UAT>PROD)
auditing of JEMH Profile configuration, enabling a difference to be seen, and even undone.
ability to set core issue properties through “Directives” during create/comment from the sending email
have users defined in a user directory like Active Directory? JEMH can autocreate users from details in your user repositories, as well as auto-resolve ‘main’ address from a senders ‘proxy’ address.
through ActiveDirectory, dynamically resolve distribution group email addresses to their constituent members for use in the issue (eg as watchers) to stop mail loops to the mailbox address.
scripting support for complex mapping logic (when subject has X and sender is Y etc)
map email content to fields using inbuilt features like Regexp Field Processor, automated ingestion of content from 3rd party issue trackers, map such content to a nominated Jira issue
scripting support to get low level fully custom access to the body of the incoming email, in order to extract values that will populate custom fields.
scripted decisions can be made on whether to drop a given mail or allow it to be processed
ever wanted an issue to look more like the email that created it (ie inline images?) well, JEMH can do that too.
ad-hoc notifications allow authorised users to mail to customers right from the issue, retaining ability for inbound images and static attachments.
whilst somewhat advanced, there is a published API for JEMH, you can extend core functionality through your own plugins to add new behaviour if needed.
want to provide a management gate single “approve/deny” button by email that a nominated email recipient can just click without having to login? JEMH “DirectiveSets” feature can do this
Outbound
per-project customization of notification content via “Template Sets” and low level control of styling
ability to retain inline images from issue descriptions/comments rendered inline, and/or attachments added to the issue
“Static Resources” enables inclusion of static content to inject images for email footer use or PDF terms
coming real soon to 3.1.x will be an ability to notify JSD customers with a JSD-like template, enabling JEMH to fully take over JSD notifications.
ability to drive notifications to Slack and SMS, with custom templates of course.
varying the From: and Reply-To: address is possible in JEMH subject to your mail server allowing it. Its also possible for this value to be setup on the way ‘in’ and used on the way ‘out'.
If you have an email processing problem with Jira, JEMH can likely help!