JEMH 5.0.0 Release Notes
- Finn Gale
Changes from JEMH 4
Default Reporter
The Default Reporter is now a Project Mapping Configuration option, allowing the default reporter to be set on a per project level. The Functionality for a ‘Global’ Default Reporter still remains via the Default Project Mapping Reporter which will be inherited by every other Project Mapping, and used if the Project Mapping does not have its on Default Reporter. Found at:
JEMH > Profile > Project Mappings > Default Project Mapping > Project/Issue > Issue Attributes > Reporter
Note: Existing Default Reporter configured in your Profile will automatically be moved to the Default Project Mapping when upgrading to JEMH 5.x. If you already have a reporter in this field, the Default Reporter will not be overwritten, using the existing Reporter.
Deprecations
Status Notifications
Status Notifications allowed email-only users to receive some periodic notification of what their open issues are, however this feature has gone widely unused and has therefore been removed.
Server Licensing
As Server is no longer supported (since Feb 2024) , the Licensing section is being removed. All licensing is now handled via the Atlassian Marketplace.
On Comment Custom Event
This param is being removed as its use is questionable, and from a support perspective has been shown to be the cause of many new user configurations triggering duplicate notifications.
Upgrading
JEMH is upgraded via the Manage Apps Screen of Jira. Found at:
Jira > Administration > Manage Apps > manage apps
Once on a compatible version of Jira or JSM 10, simply, click on the ‘Update’ button for JEMH to upgrade to our latest compatible release:
As with any upgrade between major versions, we recommend following Atlassian's guidance on upgrading Jira, ensuring you have a backup of your Jira instance:
We do not expected any specific issues related to an upgrade to JEMH 5.x however we would always advise caution as an upgrade is 'one way', both for Jira and JEMH.
We have validated upgrades from Jira 9.x (both LTS and latest versions) to 10.x, and Jira 8 to Jira 10, with corresponding JEMH upgrades and found no specific issues.
Release Summary
JEMH-8625: Data Center 7 Compatibility
JEMH-8843: Minor Compatibility fixes
JEMH-8869: Additional Compatibility fixes/ tidy up
JEMH-8557: On-boarding Wizard re-written in React
JEMH-8577: Date-picker in project setting now using correct locale
JEMH-8622: Separation of public and internal code use for Blocklisting
JEMH-8719: Catch email address radio selection for Catch address type, i.e. Plain text or Regexp
JEMH-8742: Added JQL query to the Configuration summary view
JEMH-8800: Resolved integration test framework incompatibility with Platform 7
JEMH-8832: Prevent Wizard popup for unlicensed instances
JEMH-8835: Multipart Emails now supported via the PublicApi
JEMH-8836: Sender address resolution better handles broken addresses
JEMH-8848: Removed OnComment Custom Event
JEMH-8854: Improved notification Mapping access from the DB
JEMH-8855: Support base64 encoding/decoding
JEMH-8860: smime.p7s files are no longer attached to issues where they shouldn't be
JEMH-8862: Resolve Velocity Allow list issues introduced by Platform 7
JEMH-8867: Added Cluster cache for Blocklisting
JEMH-8871: Fixed Static resource import failure
JEMH-8874: Code cleanup for major release
JEMH-8737: Migrated Profile level Default Reporter to Project Mappings
JEMH-8876: Upgrade tasks for Default Reporter Project Mapping migration
JEMH-8877: Allow JEMH to extract and check multiple In-Reply-To message-Ids for issue association
JEMH-8360: Removed Status Notifications