Excerpt | ||
---|---|---|
| ||
JEMH provides Enterprise message handling features for your |
Jira, including auditing, flexible message routing and more. |
Name
All of your email needs in Jira
The Enterprise Message Handler for
Jira (JEMH)
JIRA Compatibility
From 5.0 onwards see Marketplace for current JIRA releases
Support
Ask a question, raise an issue or email us for support
License
Commercial, get a free evaluation license via the installed JEMH add-on 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
Gliffy | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Page Tree | ||
---|---|---|
|
Overview
The Enterprise Message Handler for JIRA (JEMH) provides key business enabling functionality for your JIRA. It currently supports several communication channels including Email, HipChat, SMS and soon XMPP.
JIRA Mail handling v.s JEMH enhanced handling
JIRA Mail Handler
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.
Manipulate issues via email
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.
Powerful Field Processor system
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.
Multi-channel notification capabilities
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
Control the routing of Email to projects
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.
Improve help desk efficiency
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.
Info |
---|
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. |
Filter out spam from your Jira
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.
First-class support
Open a support request or contact us via email. We are always happy to help!
Comparison with the standard mail handler
Jira mail handler | Enterprise Message Handler for Jira |
---|---|
| Inbound |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ad-hoc notifications
Post Function notifications
|
Event Listener
The Event ListenerOutbound emails Its powerful event-based notification system can react to issue |
and user events |
and generate notifications for them |
. |
Compatibility
JEMH has compatible versions for JIRA 5.x and newer. In recent times, each minor version of JIRA released has a corresponding minor version of JEMH (JEMH 2.0 for JIRA 7.2, JEMH 2.1 for JIRA 7.3 etc.). However, this may not always be the case - check the Marketplace for compatibility details! Learn more about upgrading JEMH.
Transports
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 plaintext content is possible. From JEMH 2.0 onward, the following are available free of charge:
- HipChat Notification Transport - Send notifications with simple or rich content (including images) via Atlassian HipChat
- SMS Notification Transport - Send notifications via popular SMS providers to mobile devices
- XMPP (coming soon)
Configure JEMH to your needs
JEMH has a full user interface for real-time customisation of all features. Configurations can be exported/imported for easy migration between environments.
Control the routing of Email to projects
Default JIRA mail handler implementations are not scalable. With project, issue and user numbers rising, you will be seeing your mail server beginning to creak under the poll load, and JIRA issue creation slow down. JEMH solves this with Project Mappings, allowing routing rules based on addressee or sender email address, sender group membership or email content. All the while, allowing control over the attributes of created issues:
Enabling JIRA as a Helpdesk
Using JIRA as a Helpdesk 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 TemplateSets, can notify remote users of these changes.
Info |
---|
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. |
Reducing Spam in your JIRA
So often JIRA's around the world get bombarded by various automated responses, e.g. Out of Office. At the least this can be distracting trying to trace an issue, at worst, it may cause email loops (though Precedence: bulk should help identify such traffic). JEMH global subject blacklisting can stop that from ever happening.
Manipulate issues with Directives
Directives allow remote users/automation solutions to manipulate issues through email. With several formats to choose from JEMH can be the email integration glue required to join disparate systems to JIRA.
Powerful Field Processor system
JEMH extracts 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.
|
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 |
Useful Links
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
Recent updates | ||||
---|---|---|---|---|
|