Upgrading from Jira 6.4/JEMH 1.7 or earlier? If the version of your Jira is below 7.0 (meaning your version of JEMH is below 1.8), please upgrade Jira to 7.0 and JEMH to the latest in that series (1.8) first:
Failure to follow the above upgrade path may lead to database inconsistencies that prevent the app from functioning, as old upgrade tasks have been removed. |
JEMH 3.0.0 is the first compatible release for Jira 8. This release includes new features and an overhaul of the user interface in various configuration areas. Future JEMH 3.0.x releases will further improve the user interface and on-boarding of new users to the product, along with other new features and improvements.
Previous versions of JEMH used a horizontal navigation menu. Due to the widespread use of wide-screen displays we have decided to move to vertical navigation menus in JEMH 3.0.0. Vertical navigation allows us to make better use of vertical screen real estate.
Test Cases are one of the most commonly used features in JEMH, they assist users in testing JEMH configuration without having to configure JEMH to use a real email handler.
Fast iteration of configuration can be achieved by running a Test Case email against configuration whilst simultaneously making configuration changes. The new user interface makes this even faster by enabling Test Cases to be re-executed without a page reload.
We have also redesigned the Test Case run report (which is shared with inbound email auditing). Old processing hint data has been removed, and all relevant information is now broken down into individually named report sections.
Auditing is the central location to view JEMH processing activity and to diagnose processing problems. The new auditing interface allows querying auditing records with various filters to aid administrators in locating relevant audit entries.
In the past Jira Service Desk has required additional user configuration for customers to be able to interact with JEMH, from JEMH 3.0.0 onward this is no longer required.
JEMH will now use the Service Desk Customer - Portal Only permission entity, which means that Service Desk customers should be able to create/update issues via JEMH with no additional configuration. This also solves additional complications with Jira Software users who also want to interact with Service Desk issues as customers.
https://thepluginpeople.atlassian.net/browse/JEMH-5962
https://thepluginpeople.atlassian.net/browse/JEMH-4683
https://thepluginpeople.atlassian.net/browse/JEMH-5277
https://thepluginpeople.atlassian.net/browse/JEMH-6757
https://thepluginpeople.atlassian.net/browse/JEMH-6865
https://thepluginpeople.atlassian.net/browse/JEMH-6659
In JEMH 2.7.x we deprecated the issue creation notification feature in profiles. The profile notifications have been superseded by the "Notifications" section of JEMH. If you find that issue creation notifications are not being sent post-upgrade, you should configure notification mappings within the "Notifications" section.
Event Listener was the name previously used for the configuration section for outbound JEMH notifications. The previous name was too technical for the average user so we have renamed the section to "Notifications" which is easily identifiable for new users.
Historically catch email addresses could be configured in profiles via two fields, "Catch email addresses" and "Catch email address regexes". For a while now JEMH has been treating the contents of both catch email fields the same, so in 3.0.0 we have merged the fields into one.
Catch email addresses are no longer configured via text field in CSV, this means that commas can now be used in catch email address expressions! You can dynamically add and remove individual catch email addresses using a new user interface.
Previously to view a list of Project Mapping's you would need to enter the Projects section of a profile. This list is now available in the sidebar whilst editing a profile.
Previously this message filter would allow Non-Jira users to comment on issues if there were no Non-Jira sender or recipient custom fields defined in the profile. Now, the email will be filtered in this situation. In order to continue to allow this behaviour, the setting Security > Allow Anonymous Commenting must now be enabled.