Fixed a problem when original email is attached in JIRA as email.eml, the attached eml file name in comments does not match the real name.
This app has been archived
You may still get support information and download previous versions of this app. Learn more.
Last modified 2018-03-08 • 3150 downloads • By beagBIZ Tech
Support
To check known issues (or if you want to file one), view this app's issue tracker.
To learn more about the app, you should:
- Read the documentation.
- Look around the forums.
This is a supported app, so you may contact the vendor (or support contact) for help:
Description
Configure issue created from email
EMH can configure Custom Fields, Version, Labels, Issue Security, Reporter, Assignee and Headers when an issue is created from incoming email.
Configure comment created from email
EMH can configure Comment Visibility, Reporter, Headers, Strip Quotes when a comment is created from incoming email.
Fallback options available when setting becoming invalid
Fine tune Attachment added from incoming email
EMH can attach your original email as an attachment of created Issue/Comment.
EMH can manage attachments in incoming emails.
Duplicate attachment can be ignored.
Specific files can be ignored.
More details
EMH functions:
- Support Agile!
- Configure Custom Fields
- Pause/Disable individual handlers
- Control when to create comment or issue
- Handles Email with no subject
- Replace Tokens with email sender or address
- Configure Priority
- Configure Fixed Version/s
- Configure Affected Version/s
- Configure Component/s
- Configure Label/s
- Configure Assignee: default assignee, reporter, specific user and more
- Configure reporter: Specific user, anonymous, ignore none user and more
- Anonymous mode
- Configure Issue Security Level
- Configure Comment Visibility
- Smart Attachment Management
- Attach original email as an attachment in created issue or comment
- Prefix Email meta-data Headers in Jira description and comment body for downstream script/plugin processing
- Stop commenting on resolved issue
- Smart quote striping, handle Microsoft email format
- Support renaming of User/Version/Component and other settings
- Support configuration longer than 255 chars
For feature request and bug report, please visit our Service Desk.
Version history
1.5.8.5Jira Server 6.3 - 7.8.42017-10-19Patching Release: fixing original email attachments name mismatch 1.5.8.4Jira Server 6.3 - 7.5.42017-09-19[FIXED] Elegant Large Email/Attachment Handling This release replaces 1.5.8.3 which has been removed.
If you are experiencing large email/s stuck in your inbox, please apply this upgrade.
- Fixed description display issue(introduced in 1.5.8.3) when creating new issues
- When any of the attachments exceed Jira system attachment size limit, that particular attachment will be skipped, rest of the attachment will be processed.
- For any skipped attachment, a comment will be created on the Jira issue and the original email will be forward to the forward email address if set
- Added a new option to do not add email content as issue description and do not attach original email. This is aimed to deal with frequent large emails/attachments
- Lower Jira versions did not respect attachment size limit, this has been addressed for Jira 6.3+
- Bug fixes related to processing large emails/attachments
- Fixed few validation issue when project has been deleted
1.5.8.2Jira Server 6.3 - 7.4.62017-05-22Performance Fix for: timeouts, server hangs and can't edit handler This release fixed a known performance issue when Jira has large number of projects and custom fields combination.
This will fix various timeouts, server hangs and blank edit config page problems.
@Jira admin: if you had problem with previous 1.5.X release and have to stay on a lower version. This release is your fix.
NOTE: Every company have very different Jira setup, especially projects/issue/custom fields combinations, the performance improvement is aiming for the general cases. There might be edge cases that's not covered, if your Jira setup unfortunately fall into those edge cases, please let us know by sending us a support ticket.
We will follow up with you on your detailed Jira setup and provide corresponding improvements if necessary.
1.5.8.1Jira Server 6.3 - 7.3.92017-01-30Jira 7.3.X Compatibility Release Minor update to support Jira 7.3.X
1.5.8Jira Server 6.3 - 7.2.152016-11-23EMH goes Agile! - [EMH-61] EMH now can set Epic Link, Epic Theme and other Jira Agile fields when creating issue
- Please make sure the project is agile enabled.
- Make sure you screen layout will display Epic Link, otherwise it will be set, but hidden.
- The relevant configuration can be found in Custom Fields section as they are system build in custom fields!
- Minor UI fixes related custom fields error handlering
- [EMH-61] EMH now can set Epic Link, Epic Theme and other Jira Agile fields when creating issue
1.5.7.1Jira Server 6.3 - 7.2.152016-09-14Smart Stripe Quote option just got smarter! DESK-65: improve parsing logic to handle few edge cases when striping quoted Microsoft formatted html emails
1.5.7Jira Server 6.3 - 7.2.152016-08-22Ignore emails from none Jira user - DESK-65: customer request, adding options to only process email sent from registered Jira user email addresses; ignore emails from addresses does not belong to any Jira user.
- Support convert existing Jira build in mail handlers into EMH handler
- Support convert EMH handler into Jira build in mail handlers
1.5.6.1Jira Server 6.3 - 7.1.102016-08-04HOTFIX, very hot - error handling for multi handler config overwriting issue. This error will happen when configure multi handlers in different tabs of same browser session. Due to Jira framework limitation, the root of the problem can not be fixed within EMH. This fix contains error handling to prevent the issue from happening by disable Save when multi handlers being configured same time in same session. If you do need to configure more than one EMH at same time, please use different browsers to create different session for each handler. If you have encountered this issue already, you will have to delete your problematic handler by:
- System Administration
- locate Services section on the bottom left of the navigation bar on the left of the page
- click on services and locate the service with same name of that handler you need to delete
- delete the service
- this will in turn resulting jira to delete the EMH handler.
- fixed encoding problem when add non UTF-8 email as attachment
- Jira 7.2.0 compatibility
- error handling for multi handler config overwriting issue. This error will happen when configure multi handlers in different tabs of same browser session. Due to Jira framework limitation, the root of the problem can not be fixed within EMH. This fix contains error handling to prevent the issue from happening by disable Save when multi handlers being configured same time in same session. If you do need to configure more than one EMH at same time, please use different browsers to create different session for each handler. If you have encountered this issue already, you will have to delete your problematic handler by:
1.5.6Jira Server 6.3 - 7.1.102016-06-11To be or not to be? Issue or Comment? - adding options to only create comment or always create issue
- add support for Jira build in label picker custom fields
- enable notifications for comment creating
1.5.5.1Jira Server 6.3 - 7.1.102016-05-25[HOTFIX] cascading select custom field init issue Fix an issue where certain custom fields combination will result cascading select field not being init properly.
This is an UI fix, please make sure clear your browser cache after upgrading EMH.
1.5.5Jira Server 6.3 - 7.1.102016-05-23More Custom Field Support and CC Watchers Fine Tune! - EMH now supports Cascading Select custom field
- CC watcher option was adding both TO and CC recipients as watcher. Now it has been split into two options: TO watcher and CC watcher, which will only add coresponding recipients as watcher
1.5.4Jira Server 6.3 - 7.1.102016-05-12Stop commenting closed issue and more Custom Fields support! - Add a new option to stop or allow EMH creating comment on resolved issue
- Support Radio Buttons Custom Field
1.5.3.1Jira Server 6.3 - 7.1.102016-05-05[HOTFIX] handles email with no From header or invalid From header. This release fixes an issue introduced in release 1.5.3, where token replacement will not work when From header is missing or invalid in the email.
1.5.3Jira Server 6.3 - 7.1.102016-05-04Set sender name or email in a custom field! - EMH now supports multi-line text area
- Tokens can be used in EMH custom field settings, they will be replaced at run-time. Current supported token including sender email and sender name. Feel free to raise a service desk ticket if you need more tokens supported!
- EMH footer notes now are configurable
1.5.2Jira Server 6.3 - 7.1.102016-04-26More Custom Field Support: multi checkboxes Support Jira build-in multi checkbox custom fields.
1.5.1Jira Server 6.3 - 7.1.102016-04-20Custom Filed single select and original email as attachment option enhancement - EMH-98 EMH now supporting Jira build in single select custom field. Default value will be used if select option become invalid at run-time; remain unset if default value is not set. Select "None" option if you want to keep the option unset.
- Attachment created from original email now can be recognized by email client and will not be opened in browser as a text file. The attachment will have unique name, so when they are downloaded in a zip, they can be handled properly.
1.5.0Jira Server 6.3 - 7.1.102016-04-11BOOM! Custom Fields support is coming! EMH now supports Jira build in Custom Fields. Single line text and multi choice select are the first to be supported by feature requests. All other Jira build in custom fields will be added in following releases. Feel free to raise a support ticket if you need a particular type sooner!
- Single line text: default value will be used if nothing is set on handler config page.
- Multi choice select: default value/s will be used if nothing is set on handler config page. Select None option to avoid apply default value and leave the custom field un-selected
1.4.6Jira Server 6.3 - 7.1.102016-02-19konichiwa! -- i18n release - adding Japanese translation
- fixing typos in other languages
1.4.5Jira Server 6.3 - 7.1.102016-02-15Jira 7.1.0 compatibility release EMH now supports Jira 7.1.0
1.4.4Jira Server 6.3 - 7.0.112016-02-07Ni Hao & Ciao! - Happy Chinese New Year!
- i18n release, supporting Simplified Chinese and Italian.
1.4.3Jira Server 6.3 - 7.0.112016-01-31Support Issue Priority This is a Priority Release!
Not that this release is particular significant than others, but it does support configurable priority.
Created issue will have the specified priority if the reporter have permission to set priority.
If Use Email Priority option is selected, email priority will be used to determine issue priority. Normal email priority will map to the middle priority in Jira. Highest email priority will map to highest priority in Jira. High email priority will map to second highest Jira priority, so on so forth.
Fallback to Use Email Priority option if saved priority config becoming invalid.
NB. Email send from outlook.com and Gmail does not contain X-Priority header. Their priority is always normal.
1.4.2Jira Server 6.3 - 7.0.112016-01-28Disable/Pause your email handler! Don't like your income email handler? No problem, with EMH 1.4.2, you can now disable/pause your handler without deleting them.
You can enable handler later when you like it again!
1.4.1Jira Server 6.3 - 7.0.112016-01-21Smart Strip Quotes EMH now can strip quoted Microsoft email when creating comments from reply email chain.
1.4.0Jira Server 6.3 - 7.0.112015-12-18EMH is getting a facelift for Christmas! Major UI improvement and some minor bug fixes.
1.3.1Jira Server 6.3 - 7.0.112015-12-08Support Reporter with no permissions - EMH-90 When Default Reporter is selected, reporter with no permission will fallback to default reporter instead of reporting error
- EMH-86 Adding more Headers into pre-defined Header list and sort the list by Alphabet
1.3.0Jira Server 6.3 - 7.0.112015-12-06Smart Attachment Management - EMH-82: Better Attachment Management.
- Selectively adding attachment from email to issue/comments
- option to avoid duplicate attachment/s
- option to ignore logos, signatures etc...
- Body building! with enhanced CI system and unit/integration test on elastic Bamboo, EMH is stronger and robuster ever and ready for all road conditions.
- EMH-82: Better Attachment Management.
1.2.5Jira Server 6.0.4 - 7.0.112015-11-07Microsoft Outlook and other email clients support Attachment added by Attach Email option can now be opened directly by Microsoft Outlook and all other popular email clients.
Attach Email Option: Attaching original emails as a file. Headers (if enabled) will be displayed regardless of this option:
- Display email body in issue/comment created, original email are discarded, default behavior.
- Display email body and attaching original email as a file.
- Attach original email as a file, does not display email message in issue/comment.
1.2.4.2Jira Server 6.0.4 - 7.0.112015-11-05Bug Fixes and Improvements Containing various fixes and improvements for 1.2.4+ release.
Not required for EMH user with pre 1.2.4 version, but it's a good time to grab the latest and greatest EMH release!
1.2.4.1Jira Server 6.0.4 - 7.0.112015-10-31JDK 7 Compatibility EMH is not supporting JDK 7 again!
For Jira 7 Admin:
This release is compatible with JDK 8 + Jira 7. But you do not need it, as Jira 7 will always run on JDK 8.
For Jira 6 Admin planning to upgrade to Jira 7:
This release support JDK 7 + Jira 6, JDK 8 + Jira 6 and JDK 8 + Jira 7.
I strongly recommend you to upgrade to latest EMH release, so you have one less problem to worry about during your Jira platform upgrade.
For Jira 6 Admin:
If you are experiencing issues after upgrade to 1.2.4, you are probably on JDK 7. Update to this hotfix release will fix the issue.
1.2.4Jira Server 6.0.4 - 7.0.112015-10-27Jira 7 Compatibility Enhanced Mail Handler is now compatible with Jira 7.0.0!
The minimal JDK version requirement has also been changed to JDK 8+
1.2.3.1Jira Server 6.0.4 - 6.4.142015-08-26Hotfix for upgrading issue This is a bug fix release.
If you have experienced problems after upgrading from EMH 1.0.0 or 1.1 to 1.2+, please upgrade to this release immediately.
1.2.3Jira Server 6.0.4 - 6.4.142015-08-16Configure Reporter, Anonymous mode and more! - Anonymous ModeIssue, comment, attachment, labels created by EMH will display as done by Anonymous User. If the email sender address is associated with a Jira user, that user will still need to have sufficient permissions. Otherwise anonymous user will need permissions for corresponding actions. See Atlassian Documentation for details.
- EMH-83: Reporter Option
- Default User(Default Option): Selected user will be used as the reporter, if the sender address does not associate with a existing Jira user; otherwise using existing user.
- Anonymous: Anonymous Mode
- Create User: Create a new Jira user using 'From' address, if such user does not exists already. New user will need sufficient permission to create issue/comment
- Specified User: Selected user will always be used as the reporter of the Jira.
- EMH-56: Header optionsDisplay header options has been split into two options groups to allow Jira admin to only display email meta-data header in issue or comment.
- Various Bug Fixes
1.2.2Jira Server 6.0.4 - 6.4.142015-07-11new feature: add original email as an attachment in issue and comment - New Features:
- Bug Fixes:
1.2.1Jira Server 6.0.4 - 6.4.142015-06-08Supporting Data Center and Minor Bug Fixes - EMH now supports Jira Cluster(Data Center)!
- EMH-76: Fixed a bug which is also in Jira default mail handler where Default reporter with mixed case user name will resulting description footer not appended properly.
1.2.0Jira Server 6.0.4 - 6.4.142015-05-16EMH-1.2.0 : Assignee, Comment Visibility, Issue Security Level, no subject - EMH-28: Support Assignee Configurations
New issue assignee can be configured to use Jira automatic assignee(determined by Project Default Assignee and Component Default Assignee); reporter; First Jira user in CC list or a specified user. Automatic option will be used if specified option does not apply.
- EMH-32: Issue Security Level
Created issue will have specified Security Level. Supporting options: Project Default, None and all levels in current project security scheme. Project default will be used when specified option become invalid
- EMH-55: Support Comment Visibility
Comment Visibility can be set to All Users, any of the project roles or any of the groups. All Users option will be used when specified option does not apply.
- EMH-10: Handle email with no subject
Emails with no subject will be processed properly. "(no subject)" string will be used as the subject of the created Jira.
- variares bug fixes and UI improvements
1.0.0Jira Server 6.0.4 - 6.4.142014-09-16EMH-1.0.0 : Fixed Version, Affected Version, Component, Label, long config supports labels, versions and components; handles parameters longer than 255 characters.
Upcoming Features:
- Handle emails with no subject.
- Send acknowledge email.
- Support all build in fields.
- Support customized fields.
- Set issue priority based on emails.
- Conditions
1.1Jira Server 6.0.4 - 6.4.142015-04-02EMH-1.1 : Headers - Feature Request
- EMH-26: Email Headers: Prefix issue/comment with selected header for emails from non-Jira users.
This feature is designed to allow other plugin/scripts to handle issues/components created from mail better.
- Support Latest Jira release
- Bug Fixes
- Feature Request