There was an unexpected upgrade problem (bug) that wasn't found in our DEV instance on upgrade around 10.30am, we spotted it pretty quickly and re-deployed a fix. Its possible that could have resulted in some dropped outbound events, sorry if that affected you!
New Features and Improvements
- JEMHC-292 : System wide blacklist attachment by type
- JEMHC-282 : Blacklist directives that were set but ignored should be listed on the report
- JEMHC-279 : Licensing page to refer to Plan Upgrade option for increased capacity
- JEMHC-271 : Handle BCC delivered mail via alternate SMTP mail headers, such as Delivered-To
- JEMHC-264 : Improve advisory message for email user custom fields not found
- JEMHC-258 : Implement a user adjustable mail poll period (to cater for mailhosts who will block your account if you poll them too frequently)
- JEMHC-219 : Attachments in notifications are included as a permission denied HTML payload if issue security is not right (JEMHC won't include the attachment in this case)
- JEMHC-216 : Add User and Multi-User Picker custom field support in Notification Mappings
- JEMHC-207 : Localization support for JEMHC message text, and potentially your customizations! - targeted translations are mapped per-recipient via specific email domain regexps. See Localize Templates for more details.
- JEMHC-182 : Add Blog Post listing/links in JEMHC app
- JEMHC-138 : Add dynamically loaded list of system images, hash them, and block them from being attached in JIRA, refreshed daily
- JEMHC-6 : Filter outbound notifications based on a JQL expression
Bugs
This release was made today on 18th Jan and adds many new features.
Connection Timeouts JEMHC-269
Most requested was an increase in default timeout, (JEMHC had it a bit low, which was causing timeouts with services like office365) and in this release, the default value is now 30Secs for both inbound and outbound communication timeout, but, is configurable also.
Directive authorization control JEMHC-150
In the Profile > Mapping > Field Processors section, its not possible to restrict who can use Directives to set issue parameters. For JIRA users, you can add those users by lookup (If you have the JEMHC > Workarounds > User Lookup setup), or alternatively, just set sender email addresses, this allows a flexible mix of allowing set users to drive JEMHC with Directives. Currently Directives can also be explicitly whitelisted/blacklisted so users can be constrained to updating nominated fields (or not).
New User help offer
We see a lot of users install JEMHC but not actually get to the point of retrieving messages, so after 7 days with no messages retrieved/sent, JEMHC will mail out a query to see if the user needs help, linking to the wiki setup guide, and of course referring our support@thepluginpeople.com address.
Feedback for disabled connections
JEMHC previously disabled unstable mailbox connections, sometimes this was due to timeout problems, which the above, the cause was not as visible as we'd liked it to be, eg, gmail will tell you there is a security problem (triggered by the JEMHC servers being in Virginia the AWS us-east Availability Zone). As users you need to see that, there is a hover detail now to get this info.
Example Gmail response
530-5.5.1 Authentication Required. Learn more at
530 5.5.1 http://support.google.com/mail/bin/answer.py?answer=14257
Plan Upgrade anniversary management
Some users at the low end (JIRA user count) had message and/or data requirements that consistently exceeded their Plan allocation which is primarily a best guess based on numbers of JIRA users. The existing support for adhoc capacity through DataPacks works, but is expensive for recurring purchases, so, an additional option of Plan Upgrades has been added, as a more cost effective means of gaining increased regular capacity. Such Plan Upgrades are targeting users who expect to use JEMHC for at least a year, and are only available as an advance non-refundable non-transferrable 12 month purchase. Users existing subscription or annual costs incurred through Marketplace would be unaffected by such Plan Upgrades.