Name |
JIRA Enterprise Mail Handler (JEMH) |
|---|---|
JIRA |
5.0+ (earlier releases) |
Author(s) |
|
Homepage |
|
Support |
Confused? Need Help? |
License |
Commercial, get an evaluation license |
Purchasing |
|
Plugin Exchange |
https://plugins.atlassian.com/plugins/com.javahollic.jira.jemh-ui |
IssueTracking |
|
Downloads |
See Plugin Exchange, check your Jira revision |
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:
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 IssueEvent's to be fired, to which a JEMH IssueEventListener reacts, making use of JEMH TemplateSets, can notify remote users of these changes.
JIRA licensing is per interactive-user meaning, having a user account capable of logging into JIRA.
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.