Jira Server 5.3.0.next8 - 7.13.5
Jira Data Center 7.4.0 - 7.13.5
An enterprise grade Mail Handler for your Jira to automate ingestion of email content and customisation of outbound notifications
An enterprise grade Mail Handler for your Jira to automate ingestion of email content and customisation of outbound notifications
An enterprise grade Mail Handler for your Jira to automate ingestion of email content and customisation of outbound notifications
JEMHC Integrate email from anyone, anywhere
The Heart of JEMHC - Project Mappings
Additional Slack and SMS notifications are FREE
JEMHC provides complete notification customization capabilities (inc preview) for TEXT/HTML templates, including images, CSS, and even localisation. Templates and CSS can be bundled into Themes, for export/import.
JEMHC Profiles contain many Project Mappings, which allows specific handling based on Rules (eg recipient match). This means you can Map incoming emails To: an address, to a given project, and customize...
JEMHC now has integrated Slack and SMS transports for message delivery. These are FREE and don't count toward your Plan. Transport notifications can be customized and driven by Postfunction.
Integrate email from anyone, anywhere
Customisation of outbound notifications and more
Integrated Transports (Hipchat, SMS)
JEMH can integrate external non-Jira users, consume system generated emails, extractive fields for storage in custom fields, and much more
Configure what events should result in notifications Pick customised JEMH TemplateSets (email templates) Include attachments, inline avatars, comment images
New in 2.0, we have integrated the Hipchat and SMS transport to enable more flexible notifications. Transport notifications can be customized through TemplateSets and driven by Postfunction.
Integrate email from anyone, anywhere
Customisation of outbound notifications and more
Integrated Transports (Hipchat, SMS)
JEMH can integrate external non-Jira users, consume system generated emails, extractive fields for storage in custom fields, and much more
Configure what events should result in notifications Pick customised JEMH TemplateSets (email templates) Include attachments, inline avatars, comment images
New in 2.0, we have integrated the Hipchat and SMS transport to enable more flexible notifications. Transport notifications can be customized through TemplateSets and driven by Postfunction.
More details
Enterprise message handler for Jira Server (JEMH) provides a scalable email handling and routing, auditing, incoming mail 'fixing' on the fly, customized notification templates by project, support for email only users, integrated Test Case facilities, Auditing, configuration export/import and more.
Enterprise message handler for Jira Cloud (JEMHC) is the Cloud version.
For JEMH (Sever) pricing, please see the Licensing Page. New purchases are possible through the Shop as well as direct, discounted Maintenance/Upgrades must be done via sales@thepluginpeople.com.
For JEMHC (Cloud) pricing, please see the Marketplace Page. Core subscription processing are handled through your Jira and Marketplace only. Marketplace has no support of capacity related payments so we do related billing outside Marketplace (read more about JEMHC capacity, plans and related costs).
If you have problems with JEMH or JEMHC , reach out: support@thepluginpeople.com
More details
JEMH is an Enterprise message handler for your Jira, providing a scalable email handling and routing, auditing, incoming mail 'fixing' on the fly, customized notification templates by project, support for email only users, integrated Test Case facilities, Auditing, configuration export/import and more.
For JEMH (Sever) pricing, please see the Licensing Page. New purchases are possible through the Shop as well as direct, discounted Maintenance/Upgrades must be done via sales@thepluginpeople.com.
For JEMHC (Cloud) pricing, please see the Marketplace Page. All related purchases are handled through your Jira and Marketplace only.
If you have problems with JEMH or JEMHC (we dogfood our JEMHC addon for this)
- JEMH (Server): jemh-support@thepluginpeople.com
- JEMHC (Cloud): jemhc-support@thepluginpeople.com
More details
JEMH is an Enterprise message handler for your Jira, providing a scalable email handling and routing, auditing, incoming mail 'fixing' on the fly, customized notification templates by project, support for email only users, integrated Test Case facilities, Auditing, configuration export/import and more.
For JEMH (Sever) pricing, please see the Licensing Page. New purchases are possible through the Shop as well as direct, discounted Maintenance/Upgrades must be done via sales@thepluginpeople.com.
For JEMHC (Cloud) pricing, please see the Marketplace Page. All related purchases are handled through your Jira and Marketplace only.
If you have problems with JEMH or JEMHC (we dogfood our JEMHC addon for this)
- JEMH (Server): jemh-support@thepluginpeople.com
- JEMHC (Cloud): jemhc-support@thepluginpeople.com
Reviews for cloud
(69)Sign in to write a review
Thanks for some kudos to what JEMHC can provide. Sorry you found cloud pricing objectionable, perhaps a hosted Server instance would suit better, you bear all service provision, ongoing maintenance and upgrade costs? The comments made about costs of data may miss the point of why pricing for data volume is there at all. We allocate Plans that always cover 99% of users in a tier with no additional cost and still allow for excessive data usage through PlanUpgrades and DataPacks. Data levels are not merely for 'storage' (and cannot be equated simply to S3 bucket costs) but represent real and actual performance impact to the system; all mail is read, pulled apart, encrypted, stored in the database, written to Jira, or external storage (soon). Its a computational load far in excess of simplistic storage in S3.
You found your instance in a low-user high-volume usage situation, with over 2X the volume of anyone in your tier or the next two IIRC. JEMHC can support your much larger than average data volumes, but it will cost you more. It would be far more cost effective to run your own JIRA instance (even host in AWS yourself) with a 25 user JEMH Server license costing $500. Of course, _you_ will have to manage it, maintain it etc.
Oh, gmail is free because you are the product. We have zero interest in data mining your email content.
Thanks! Yes, we are carrying some technical debt in UI complexity :/ new user feedback noted, we'll be doing some videos (sooner) and wizard link bootstrapping (a bit later)
Reviews for server
(69)Sign in to write a review
> They keep censoring reviews as well and simply flag and remove the review if they disagree with its content. Very unprofessional behaviour.
No, its not about disagreement with your view or not liking it, we kept flagging your re-posted comments for quite professional reasons:
- it was left for the wrong product (JEMH is available for Cloud, Server and DC, we think this is more related to DC but heck, we'll let that slide)
- it contained what we considered unwarranted defamatory content
- it contained unrelated material to the point you're making (other peoples comments about other products)
If we do flag a comment (not something we need to do often), it is only for Atlassian to judge what is appropriate and what is not. We welcome all feedback and hope to learn from any scenario that doesn't meet our high standard. We are proud of our positive feedback average gained over the last 7 years. We feel your current 1* review is therefore overly harsh and hope you will reconsider this at some point.
> Documentation is not up to par nor is transparency into this change
No, we published our Data Center licensing migration docs on the JEMH Licensing page nearly 10 months ago and have made continual updates since. FYI, as a vendor we have often wanted to determine what customers were actually using Data Center, such information was never available, so we had no method to reach out.
> They blamed things on Atlassian's "broad strokes"
No, we didn't. All we have done is consistently point out you are misinterpreting the Atlassian docs related to Marketplace issued Server license transition to Data Center. You talk of us "not honouring" a 50% discount, this is factually incorrect as it does not apply to JEMH specifically as it has never had a JEMH Server license on Marketplace (confirmed by Marketplace staff at DC app launch).
> and refused to work with us to find a suitable resolution.
You didn't exactly give us much choice. To recap, you demanded a 50% discount due to your viewpoint, we declined, and so you logged a 1* review.
Reviews for Data Center
(69)Sign in to write a reviewThanks! Yes, we are carrying some technical debt in UI complexity :/ new user feedback noted, we'll be doing some videos (sooner) and wizard link bootstrapping (a bit later)
Cloud Pricing
Server Pricing
Data Center Pricing
This app is sold by a third-party vendor.
Let us know that you'd like to manage this app's billing on your Atlassian invoice.| 50 users$900/year | 100 users$1,600/year | 250 users$3,200/year | 500 users$4,800/year | 750 users$5,400/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does cloud app pricing work?
Cloud apps are sold as a monthly or annual subscription. You are eligible for support and automatic version updates as long as your subscription is active.
When your subscription renews each month, you are automatically billed for apps based on the number of users in your instance.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my cloud pricing?
Apps are billed based on the number of users in your Atlassian product. Jira Cloud apps are priced based on the maximum users of the Jira products on your instance. For example, if you have Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you pay the 50-user price for apps.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for licensing across maximum users still apply.
The pricing structure for cloud apps is as follows:
- Monthly subscriptions with up to 10 Atlassian product users are billed at a flat rate price.
- Monthly subscriptions with more than 10 users are billed per user, starting at the first user.
- Monthly subscriptions with more than 100 users are billed per user. The table above provides example pricing at various user levels.
If you've opted for annual billing for your Atlassian product, apps are also billed annually at a discount (12 months for the price of 10).
- Do you offer academic, community, or open-source licenses for cloud apps?
Academic, community and open source licenses are not available for cloud apps.
- Can I extend my free trial?
For cloud apps, you cannot extend your free evaluation period. All cloud apps are immediately subscribed by a user, and we provide a free evaluation period. This is a minimum of 30 days and ends on the second billing cycle after you first subscribe to the app.
Pricing FAQ
- What does 'paid-via-vendor' mean?
Paid-via-vendor apps are licensed and purchased directly through the vendor who makes this app.
Payment for paid-via-vendor apps is not handled by Atlassian.
- Will paid-via-vendor transactions be on my Atlassian invoice?
Paid-via-vendor transactions are not managed by Atlassian. This means transactions for paid-via-vendor apps will not be on your Atlassian invoice.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
The Plugin People provides support for this app.
The Plugin People is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
The Plugin People is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Collaborative documentation platform hosted by this vendor.
Community discussions connect you to the vendor and other customers who use this app.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Jira Cloud • Released 2019-06-07
Summary
Required scopes changed
Details
Required scopes changed:
- Added: ACCESS_EMAIL_ADDRESSES
Versions
Version 3.0.14-server • Jira Server 8.0.0 - 8.2.4 • Released 2019-05-29
Summary
Bug fixes, new features and improvements
Details
- JEMH-7021 - Only first 50 organizations are displayed and settable via Custom Field Defaults
- JEMH-7044 - Strike and colour parsing failure from html mail to wiki markup
- JEMH-7046 - CSV field processor reports failure if "issueKey" field value is empty string
- JEMH-7047 - Processing report does not show all created/updated/commented issues in multi-issue outcome
- JEMH-7051 - RegexpFP reporter click through hardwired to /jira/ should have been contextPath
- JEMH-7058 - Auto join groups audience field in ProjMap not saving/retrieving the right selector
- JEMH-7067 - In Jira User Notification, templates have to be selected if you want to drive Non-Jira user notification
- JEMH-6654 - Auditing of profile configuration changes
- JEMH-7043 - Auditing of template set changes
- JEMH-7045 - Option to remove from HTML mail (for v2 standard extract)
- JEMH-7061 - Ability for profiles in a profile group to ignore processing outcome to allow further profiles in the group to run
Versions
Version 3.0.16-dc • Jira Data Center 8.0.0 - 8.2.4 • Released 2019-07-03
Summary
Bug fixes, improvements and new features
Details
- JEMH-7099 - Re-implement the "Delete All" action for Incoming Mail in Auditing
- JEMH-7026 - Allow administrators to control visibility of Ad-hoc window settings tab
- JEMH-7094 - Allow overriding the forward user with the Project Lead
- JEMH-7103 - Copies of a profile should have profile revision 0 instead of revision of original
- JEMH-7104 - Editing a Profile Group member Profile displays "jemh.profiles.edit.title" rather than the correct translation
- JEMH-5081 - Set From: address Personal via velocity statement
- JEMH-7106 - Issue update validation failed does not log fields + value
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Enterprise Mail Handler for Jira (JEMH) via search. Results include app versions compatible with your Jira instance.
- Click Install to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
To find older Enterprise Mail Handler for Jira (JEMH) versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Add-ons. The Find new apps or Find new add-ons screen loads.
- Locate Enterprise Mail Handler for Jira (JEMH).
- Click Free trial to download and install your app.
- You're all set! Click Close in the Installed and ready to go dialog.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Enterprise Mail Handler for Jira (JEMH) via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Enterprise Mail Handler for Jira (JEMH). You're prompted to log into MyAtlassian. Enterprise Mail Handler for Jira (JEMH) begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Enterprise Mail Handler for Jira (JEMH) versions compatible with your instance, you can look through our version history page.
Similar apps
