Excerpt | ||
---|---|---|
| ||
JEMH provides Enterprise message handling features for your JIRA, including auditing, flexible message routing and more. |
Name | Enterprise Message Handler for JIRA (JEMH) |
---|---|
JIRA | |
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
JEMH is an The Enterprise Message Handler for JIRA that (JEMH) provides key business enabling functionality for your JIRA. Currently JEMH It currently supports several Transports such as communication channels including Email, HipChat, SMS and soon XMPP. Examples of some of this functionality are shown below:
JIRA Mail handling v.s JEMH enhanced handling
JIRA Mail Handler | JEMH Mail Handler |
---|---|
| Inbound Mail Handler
Ad-hoc notifications
Postfunctions
Event Listener The Event Listener can react to issue events as well as user events, and generate notifications for them. Configuration of notifications can be done on a per-project basis, or globally. Events can be enabled individually, and custom templates if created may be selected over the default JIRA template. Its also possible to script mutation of the event, to 'decide' that because issues have certain properties, that a custom Issue Event needs to be fired (sending a different notification). |
Compatibility
JEMH has compatible versions for JIRA 5.x and newer. Generally for each minor version of JIRA released, there will be a corresponding minor version of JEMH (e.g. JEMH 1.8 for JIRA 7, JEMH 1.9 for JIRA 7.1). Always check the Marketplace for compatibility details! For more information, see the Upgrading JEMH page.
Transports
A relatively new feature is support of pluggable transport layers, which extend JEMH's notification capabilities beyond email. Each Transport hooks into the Event Listener, can have per-event enablement, and customized template content in text or html. From JEMH 2.0 onwards, the following are available free of charge:
- HipChat - Supports Text and HTML including images
- SMS - Supports notifications via popular SMS providers
- 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.
Route your mail
Default mail handler implementations are not scalable, with project numbers rising, you will be seeing you mail server beginning to creak under the poll load, and JIRA issue creation slow down. JEMH solves this with Project Mappings, allowing arbitrary configurations based on addressee or sender email address, even sender group membership, in order to route to a target project. Created issues can be tailored as appropriate:
Gliffy | ||||||
---|---|---|---|---|---|---|
|
JEMH 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. |
Gliffy | ||||||
---|---|---|---|---|---|---|
|
JEMH 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.
Gliffy | ||||||
---|---|---|---|---|---|---|
|
JEMH 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.
Gliffy | ||||||
---|---|---|---|---|---|---|
|
JEMH Field Processors
JEMH has several Field Processors, each tailored to processing emails in a particular format. There are many generic formats available for inbound issue creation. Some system-specific custom integrations are also available, and will be expanded in future.
Gliffy | ||||||
---|---|---|---|---|---|---|
|
Useful Links
- How Do I.... - An extensive and ever-growing series of guides for achieving common JEMH set-up goals
- Common Problems - Encountered a problem or error? Check this list to see if a solution is provided
- JEMH Issue Tracker - Can't find what you are looking for on our wiki? Post an issue there, or alternatively email us
Recent updates | ||||
---|---|---|---|---|
|