JEMH provides Enterprise message handling features for your Jira, including auditing, flexible message routing and more. |
The Enterprise Message Handler for Jira (JEMH) provides a wide array of business enabling functionality, unmatched by any other handler. It allows full configuration, which can later be exported or imported for easy migration between environments. It currently supports several communication channels including Email, Slack and SMS.
Directives allow users/automation solutions to modify issues directly through email. With several Directive formats to choose from, JEMH can be the email integration glue required to join disparate systems to Jira.
JEMH can extract information from emails using Field Processors, each tailored to processing emails in a particular format. While the Field Processors that come with JEMH should cover most needs, new Field Processors can be created and integrated with JEMH via its API. This allows near infinite possibilities in terms of what can be processed.
Transports extend JEMH's notification capabilities beyond just email. Each Transport hooks into JEMH's Event Listener system and can be enabled on a per-event basis. As usual, customization of both HTML and plain text content is possible. The following Transports are built in:
Slack integration - send notifications to rooms
SMS Notification Transport - Send notifications via popular SMS providers to mobile devices
Standard Jira mail handlers are not scaleable. With project, issue and user numbers rising, mail servers are put under increased load and Jira issue creation slows down. JEMH solves this with Project Mappings, allowing you to route email to projects based on definable criteria. This criteria could be as simple as sender/recipient address, group membership or email content. All the while, allowing control over the attributes of created issues.
Using Jira as a help desk out of the box requires creation of users, but if the interaction is fleeting, and with a lot of support traffic, a significant amount of wasted seats will accrue, never mind the Jira user account 'noise'. JEMH solves this by mapping remote user email addresses to a Custom Field, and uses a "Default Reporter" to nominally create the issue on their behalf. Updates by interactive Jira-users (and remote non jira-users) cause Issue Events to be fired, to which a JEMH Issue Event Listener reacts, making use of JEMH Template Sets, can notify remote users of these changes.
Jira licensing is based on the number of interactive application users. This refers to users that own a user account capable of logging into Jira instances. |
Often you may find Jira getting bombarded by various automated responses, for example when a user is Out of Office. This problem can be a distracting annoyance. At worst, it could cause email loops or prevent legitimate emails from being processed. JEMH has advanced Blocklisting features that can stop this from ever happening.
Open a support request or contact us via email. We are always happy to help!
Jira mail handler | Enterprise Message Handler for Jira |
---|---|
| Inbound email
Ad-hoc notifications
Post Function notifications
Outbound emails Its powerful event-based notification system can react to issue and user events and generate notifications for them.
|
License | Commercial, get a free evaluation license via the installed JEMH app License section |
---|---|
Purchasing | After installation, see the JEMH add-on License section. also, sales@thepluginpeople.com |
Marketplace | https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui/server/overview |
Issue Tracking | Issues are tracked on Jira Cloud |
An extensive and ever-growing series of guides for achieving common JEMH set-up goals
Encountered a problem or error? Check this list to see if a solution is provided
Can't find what you are looking for on our wiki? Post an issue there, or alternatively email us