{excerpt:hidden=true}JEMH provides Enterprise email handling features for your JIRA, including auditing, flexible message routing and more.{excerpt}
{section}
{column}
||Name | Enterprise Mail Handler for JIRA (JEMH) |
||JIRA | 5.0+ ([earlier releases|Pre 1.0 Content]), [see Marketplace for current JIRA releases|https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui] |
||Author(s) | [~abrook] |
||Homepage | [this page|https://thepluginpeople.atlassian.net/wiki/display/JEMH/JEMH+Home] |
||Support | Confused? Need Help? [!getsatisfaction.png!|https://getsatisfaction.com/thepluginpeople/products/javahollic_jira_enterprise_mail_handler]|
||License | Commercial, get an [evaluation license|3 - Licensing]|
||Evaluation | 30day Evals are available from the JEMH plugin License form|
||Purchasing | After installation, see the JEMH plugin License form|
||Marketplace | [https://marketplace.atlassian.com/plugins/com.javahollic.jira.jemh-ui] |
||IssueTracking | [OnDemand|http://thepluginpeople.atlassian.net/browse/JEMH] |
||Downloads | See Plugin Exchange, check your Jira revision |
{column}
{column}
{gliffy:name=JEMH Functional Overview|align=left|size=M|version=4}
{column}
{section}
h2. JEMH Overview
JEMH is an Enterprise Mail Handler for JIRA that provides key business enabling functionality for your JIRA. Examples of some of this functionality are shown below:
h3. Compatibility
JEMH has compatible version for JIRA 5.x and up. Sometimes API changes in JIRA mean that JEMH has to break backward compatibility, so, the latest version will not necessarily work for older JIRA releases, and this becomes more true the further back you go. Always check Marketplace compatibility!
h4. JIRA6 Upgrades
For those coming to upgrade to JIRA6, the JEMH 1.4.x releases are required, and are not backward compatible with JIRA 5.x. See the [Upgrading JEMH]
h3. Configure your JEMH
JEMH now has a full user interface for real-time customisation of all features, the legacy configuration file is deprecated. Configurations can be exported/imported for migration between environments.
!jemh-config-screen.png|thumbnail!
h3. 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:name=JEMH Inbound Mail Routing|align=center|size=L|version=5}
h3. 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 defaultReporter to nominally create the issue on their behalf. Updates by interactive JIRA-users (and remote non jira-users) cause IssueEvents to be fired, to which a JEMH IssueEventListener reacts, making use of JEMH TemplateSets, can notify remote users of these changes.
(i) JIRA licensing is [per interactive-user|http://www.atlassian.com/licensing/jira#downloadlicenses-7] meaning, having a user account capable of logging into JIRA.
{gliffy:name=JEMH enabling JIRA for Helpdesk use|align=center|size=L|version=5}
h3. 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:name=JEMH Reducing Spam in your JIRA|align=center|size=L|version=4}
h3. 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:name=JEMH Directive Processing|align=center|size=L|version=2}
h3. 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:name=JEMH Field Processor integration options|align=center|size=L|version=1} |