• log4j dependency tidy to explicitly depend on a single fixed log4j patch version provided by the Jira platform (1.2.17-atlassian-13) in this case.

• EMQ-427 : Users without 'application access' are considered 'inactive' and don't receive notifications

• EMQ-419 added null checks relating to entity processing
• EMQ-415 incorrect url links to user profiles (recipient must be on same network as Jira for links to resolve)
• EMQ-409 Assertion made over issue security, so where a security level is set, regardless of whether a Jira user is resolved to be notified through the Jira notification scheme, they will not be notified if they do not have the issue security level.

• minor logging improvements to help tracability

• EMQ-405 - Dialog popups not displaying correctly
• EMQ-406 - HTML content preview not working in firefox

Some customers have experienced problems with IMMEDIATE delivery mail stuck "IN PROGRESS". This release provides two features that can assist:

1) The "Flush Failed Mails" button on the Auditing > Mail Items view now also picks up unsent IMMEDIATE delivery mail older than 5 minutes, and will result in all these being sent.

2) (In Jira Server ONLY - disabled in DataCenter, which EMQ is not yet certified) Every 10 minutes, the first 100 unsent IMMEDIATE delivery mails older than 5 minutes are sent. This feature is here to chew threw any backlog over time.

Logging has also been improved in the IMMEDIATE mail sending phase.

• EMQ-394, fix for: inconsistent datatypes: expected - got CLOB

• EMQ-392 : Fix JEMH integration bug causing duplicate JEMH notifications
• EMQ-390 : Update terminology to Inclusive and Exclusive
• EMQ-389 : solve audit event deleteAll compatibility with Oracle

• EMQ-386 - Email Settings, jql filter was a single line (50 chars or so) should be textarea

• EMQ-376 - User keys displayed in Summary of changes section in notifications

• EMQ-372 - Orphaned digest content data is created on each flush

• EMQ-365 - Outbound mail connections screen fails to render
• EMQ-368 - Pre-configured Mailtrap settings incorrect

• EMQ-366 : SQLServerException: The incoming request has too many parameters. The server supports a maximum of 2100 parameters

• EMQ-360 - Incorrect Reply-To header values set on outbound notifications
• EMQ-361 - Outbound notifications not threaded correctly for some mail clients
• EMQ-343 - EMQ converting SVG images but not changing the name of the file
• EMQ-350 - Not using 'From Personal' defined in Mail Queue for outbound mail
• EMQ-351 - Enable EWS Autodiscovery URL entry (domain url and authentication domain)
• EMQ-362 - Reduce database queries performed during removal of old sent mail items from auditing history

• EMQ-340 - schema problem resolved

• EMQ-336 : was inheriting the thread ID for reply-to address.

• EMQ-332 fix $counter in template context
• EMQ-323 fix a bug that causes some loss of body parts where multiple digest emails are involved

width / height attributes should be numeric only, not "32px"

• 1.9.0 represents quite a large refactor in EMQ, the processing has undergone rework for consistency, there are now effectively 3 processing paths i) Event processing, ii) Digesting and iii) Delivery.
• We have simplified the configuration inheritance, making it easier for system admins to inject EMQ into a project, taking over with all Immediate delivery,then users would be able to selectively opt-in to digesting of some (or all) notifications based on user-specific configuration.

• EMQ-315 : test data generator was defaulting to using the reporter, now if project has default assignee Project Lead, it will be used.

• EMQ-278 - Error when importing mail queue configuration

• EMQ-275 - Inline images not present in HTML may be attached when using immediate send mode

• EMQ-273 - Queue flush job is not being registered on plugin startup
• EMQ-274 - AO upgrade task could cause some tables to be dropped during migration
• EMQ-205 - Allow project admins to flush mail queues

• EMQ-162 - Export and import of configuration
• EMQ-246 - Queues can now have a Delivery Type of Digested or Immediate
• EMQ-255 - Keep last 100 emails in 'Sent Email History'
• EMQ-260 - Verify that the issue event handled by EMQ is not missing critical data such as issue key
• EMQ-189 - User Profile Flush My Queues Button Does Not Flush User Queues
• EMQ-261 - EMQ not rejecting API digest calls even though its configured source is only "JIRA"
• EMQ-262 - User preferences with "max events per email" and "max emails per flush" set to zero not using default values

• EMQ-256 - Digest History not being automatically purged

• EMQ-253 - JSD Event Listener is not being registered when Jira starts
• EMQ-254 - ClassCastException when JEMH and EMQ interact with the same comment issue event

• EMQ-189 - User Profile Flush My Queues Button Does Not Flush User Queues
• EMQ-261 - EMQ not rejecting API digest calls even though its configured source is only "JIRA"
• EMQ-262 - User preferences with "max events per email" and "max emails per flush" set to zero not using default values

• EMQ-260 - Verify that issue event handled by EMQ is not missing key data (event ID, issue key)

• EMQ-256 - Digest History not being automatically purged

• EMQ-253 - JSD Event Listener is not being registered when Jira starts
• EMQ-254 - ClassCastException when JEMH and EMQ interact with the same comment issue event

• When @mentions are used in comments, JIRA sends a notification not using IssueEvents (which is what EMQ primarily expects). Its not possible to hook into mention notifications at all. EMQ historically would notify all expected parties via NotificationScheme. But. When users were mentioned, they would get two notifications. This fix filters recipients if they were @mentioned in related comments. such notifications will not be sent or digested for that party for that notification. We will push this change up to the latest revision, at that time we may expose further conditional configuration based on feedback.

• EMQ-266 - Emails for the same issue do not form threads in email clients

• EMQ-253 - JSD Event Listener is not being registered when Jira starts
• EMQ-254 - ClassCastException when JEMH and EMQ interact with the same comment issue event
• EMQ-256 - Digest History not being automatically purged

• EMQ-236 : Priority icons not sized correctly in Apple Mail
• EMQ-239 : Action user profile URL not set in template context

Important: Installers of the previous version (1.5.6) should upgrade to this as soon as possible. Version 1.5.6 had a bug where Jira installations without Jira Service Desk present were unable to operate correctly with v1.5.6. This version fixes that.

• EMQ-238 - EMQ failing to start on Jira installations with no Jira Service Desk
• EMQ-233 - Convert SVG user avatar images to PNG to improve email client compatibility
• EMQ-232 - Jira priority icon images are not being converted from SVG files
• EMQ-231 - Internal JSD issue comments present on customer user digests

• EMQ-179 : createStaticUrl() for objType [Issue Type] not found in URL
• EMQ-215 : Rare occurrences of incorrect event item ordering in notification digests

• EMQ-213 : Make it clear that the bulk user participation change tool does not show current user opt in/out status
• EMQ-212 : Add Mail Queue form breaks when custom templates are present
• EMQ-206 : IssueCommentDeleted event not handled

• test-data generator wasn't including 'default' values for custom fields, which broke issue creation in projects with required fields

• EMQ-198 : Bulk user opt-in/out tool only processes first 1000 users

• EMQ-195 : New Feature - Bulk user digest opt-in/out tool. Allows admins to perform bulk user digest opt-in/out operations. For more information, see Bulk opt-in/out all Jira users for EMQ digests
• EMQ-192 : Mail connection test fails
• EMQ-191 : Exception when notification scheme not selected in Mail Queue

• The primary improvement in this release is to finally enable digesting of IssueEvent notifications from JEMH (V2.1+), meaning that customized content can be bundled up for non-Jira users, for Jira users, as well as targeted recipients via whitelist/blacklist.

• EMQ-256 - Digest History not being automatically purged

• EMQ-215 : Fix for possible event item ordering issue in digests

• EMQ-213 : Make it clear that the bulk user participation change tool does not show current user opt in/out status
• EMQ-212 : Add Mail Queue form breaks when custom templates are present
• EMQ-206 : IssueCommentDeleted event not handled

• EMQ-199 : Event processing fails when attempting to process issue with maximum length summary

• test-data generator wasn't including 'default' values for custom fields, which broke issue creation in projects with required fields

• EMQ-198 : Bulk user opt-in/out tool only processes first 1000 users

• EMQ-195 : New Feature - Bulk user digest opt-in/out tool. Allows admins to perform bulk user digest opt-in/out operations. For more information, see Bulk opt-in/out all Jira users for EMQ digests
• EMQ-192 : Mail connection test fails
• EMQ-191 : Exception when notification scheme not selected in Mail Queue

• EMQ-187 improve digest rendering

• ServiceProxyDestroyed exceptions were occurring in the logging system on upgrade as it retained a reference to the ActiveObjects service that was replaced by the new addon but not 'updated', this is now handled better, to be harmless when it occurs (just the once). Future revisions will remove this problem entirely
• Tidies up logging, makes INFO level a neater summary of whats going on (events received, messages sent, database record removal summary)
• Resolve problems with clean shutdown of addon, affecting update and enable/disable cycles
• Resolve problem observed where HTML could feed through as TEXT content in a TEXT notification

This release also includes some tweaks that are necessary for JEMH to be able drive its notifications through EMQ for digesting purposes #comingsoon!

• EMQ-176 Image attachment referral not adding attachment to digest. JSD needs special handling as the images are rendered via servlet

• In this release, the velocity context used to render the subject and body is pre-initiailized with many values expected for standard email notifications (issueManager, groupManager etc). As yet there isn't integrated velocity context documentation has there is in JEMH, but key classes are documented on the wiki.

• EMQ-169 : null contentType reference causes problem with Amazon SES

• EMQ-163 uploaded image/png issue type icons causing a stack in the log (they being considered as svg)

• The Default TemplateSet that creates the digested mail notification goes a little further in exposing the 'wrapper' markup for each included 'blob' of pre-rendered HTML (or text). This enabled us to make the 'wrapper' of each included comment include the specific HTML that Gmail requires in order to make the summary index anchor link to the content work.

Historic TemplateSets continue to work as is.

• Now EMQ will prevent digesting to inactivated recipients, as well as stopping sending to them. if they are found to be inactive at the time of flushing.

• EMQ-117 : Bulk change "Send mail for this update" option is not respected

• EMQ-116 : Default digest flush doesn't occur when User Delivery Options are more frequent

• EMQ-199 : SQL Error when attempting to process maximum length summary
• EMQ-206 : IssueCommentDeleted event not handled
• EMQ-215 : Incorrect event item ordering in notification digests
• EMQ-220 : User queue flush resets next main queue flush time

• Now EMQ will prevent digesting to inactivated recipients, as well as stopping sending to them. if they are found to be inactive at the time of flushing.

• EMQ-117 : Bulk change "Send mail for this update" option is not respected

• https://thepluginpeople.atlassian.net/browse/EMQ-104 , see wiki for details (in progress)

• Now EMQ will prevent digesting to inactivated recipients, as well as stopping sending to them. if they are found to be inactive at the time of flushing.

• EMQ-117 : Bulk change "Send mail for this update" option is not respected

• performance tweak
• minor screen refresh issue

• EMQ-102 - more logging and exception handling for queue flushing

• https://thepluginpeople.atlassian.net/browse/EMQ-102

• The default behaviour is to set the Flush time to be a nominated arbitrary periodicity, eg 1h,4h. Users requested ability to send at nominated times, eg 0900,1200. This release adds that feature. To configure, See the EMQ > Mail Configuration > Global Config > Configure Emails > Flush Type field. It can now be either (a) Periodicity or (b) Time. See Configure Email Options for a screenshot/more.

• Adds reply-to address on outbound mail connections and queues, allowing replies to be directed to a particular mailbox.
• Issue type icons and status icons that were added to Jira (did not come with the product) appear to be broken, while the 'standard' icons work when embedded, specific to Jira 6.4.x

• possible fix for unreproducible avatar rendering problems

• Adds support for inlining Service Desk project and issue-type icons, as JSD has a plugin-specific way to expose such artifacts

• https://thepluginpeople.atlassian.net/browse/EMQ-67 Some default image icons weren't loading

(i) we have open issues for JSD icons, coming soon via https://thepluginpeople.atlassian.net/browse/EMQ-73 and

https://thepluginpeople.atlassian.net/browse/EMQ-74

• a compare method was breaking, now made extra paranoid

• EMQ-71 bugfix stopping outbound mail sending

• bugfix - EMQ-67, addressing inlining custom icon/priority images

• improves outbound template rendering in the subject to use velocity

• when no creds were supplied we were setting an empty value, rather than null

• Fixes issues affecting outbound scheduled notifications

• updates EMQ for compatibility with Jira 6.3+
• adds support for datacenter features

• If an issue was deleted, problems occurred looking up issuetype for outbound rendering