V1.1.43 released
JEMHC-620 - resolves a problem where Non-JIRA email security checks were OFF that post-create cc: non-jirausers were not being added to the participant custom field
JEMHC-618 - reduce report message "Reporter not set. JIRA user with email x@y not found. Should the user be found? Have you tried user lookup workaround?" from WARN to INFO, as working around Atlassian Connects inability to do user lookup is not mandatory
JEMHC-610 - To clarify when editing rules that all the subordinate attributes relate to that rule, they have been indented, see the updated Use Priorities in Project Mapping Rules
JEMHC-609 - When Project Mapping Rule evaluation Strategy is selected (can be set globally at Profile level, and/or, defined on a per Project Mapping basis), 0 is the default (lowest) priority, users can then select between 1 and 20 that would beat the default, with 20 being lowest-defined, and 1 being top.
JEMHC-604 - Added static group selector in outbound Notification Mappings, so now, you can nominate a static JIRA group, who's recipients will be notified in addition to issue-related fields.
JEMHC-599 - Added detection for Non-Delivery bounces, with user configurable handling, to Allow / Drop / Forward (default)
JEMHC-597 - Custom Field selector in the Alias section was previously just customfield_12345, this was hard to understand, has been improved to format ID/Type: Name e.g. "customfield_12345/Text Field (multiline) : Email Participants"
JEMHC-596 - Added Priority based Rule evaluation strategy, the historic strategy was first match wins, now, some finer grained control can be had, given that Rules can be logically AND'd together, you can combine Rules at a higher priority than other single value (eg domain, or keyword) rules. See Use Priorities in Project Mapping Rules for a worked example.
JEMHC-595 The Auditing section now has a System Statistics page, currently just showing Pingdom update and Response Time stats:
JEMHC-594 Some back office functionality has been added to validate the existence of endpoints in your hosts that are critical to JEMHC working (Atlassian Connect, Webhooks)
JEMHC-593 Added capability to define input mail specific date formats in the Project Mapping Field Processors section that can then be used to parse incoming dates, enabling them to be rebuilt for the JIRA instance format.
JEMHC-592 Add more flexibility to outbound from: Personal definition so that the personal part can be (a) statically defined, eg 'Support', (b) Left empty to take on the mail server default, (c) use the display name of the 'action' user.
JEMHC-587 During issue creation, all attachments on the issue will be scoped for inclusion in notifications, rather than any time related factor. This addresses problems with speed of upload / volume of attach upload causing some attachments to be missed.
JEMHC-109 Rework Subject Field Processor, moving from a regular expression based process to a simple text parser approach - to remove the complexity and resolve edge cases that were too hard to address via regexp.