V1.0.125 deployed
This release beings in some sweeping changes to Template Sets, historically there was a single Global readonly velocity macro that had macro content used by Themes, in this release, the Themes now aggregate custom Layout (css) and Theme specific macro content that will be used in addition to a much reduced Global macro.
SOON Coming soon will be the ability to import/export Themes, which will allow users to create a composite export of CSS, Macros and select from current Template Sets of the the Theme. Importing the Theme will make everything instantly available, without new Templates needing to be created, which opens up new possibilities for 3rd party Theme generation.
Changes to Template Set structure
At this time we've also reworked the existing default Template Set structure a little, so there will be a slightly different layout in new templates, but old ones will continue to render exactly the same. Existing custom Template Sets have had copies of the original 'global' macro content added to the top so they will continue to work.
New JSD-like Theme
A new Theme has been added, which gets close to the JIRA Service Desk notification format, and allows customization to include specific custom fields etc.
JSD Support in JEMHC
Currently, JEMHC supports email only users in conjunction with JSD, supporting emails from JIRA users and JSD v2 Portal Users poses problems. There are some integration issues due to the Atlassian Connect platform and JSD itself that prevent JEMHC from being 'better' in this scenario. With no JSD source code available, testing and diagnosis is tricky, its a black box scenario; many issues have been logged:
See more: Common Problems#ServiceDeskrelatedissues
To clarify:
https://ecosystem.atlassian.net/browse/AC-1014 - JEMHC cannot lookup users without the 'workaround' user/password being set
https://ecosystem.atlassian.net/browse/AC-1080 - JEMHC cannot create issues or comments 'as' another user, and must create them as the JEMHC-Addon user, this is why issue descriptions and comments get a prefix with the remote email sender
If JSD email notifications are enabled, and JEMHC is configured for a notification audience that includes JIRA participants, duplicate emails are likely. Disable JEMHC JIRA participants in JEMHC > Notifications > Issue config, or disable JSD email notifications
https://ecosystem.atlassian.net/browse/ACJIRA-306 (fixed but not released) and https://jira.atlassian.com/browse/JSD-1484 - JEMHC will broadcast JSD 'internal' comments due to the unique way JSD implements this feature and due to bugs in how that information is (not) propagated to external addons like JEMHC. The current only workaround is to disable the service-desk-comment-field component (see link above) and use standard Comment visibility.
https://jira.atlassian.com/browse/JSD-1505 - JEMHC will create comments from anyone as JSD Internal comments (shown in the Service Desk Public/Internal comment field), due to bugs in JSD, the only workaround right now is to again disable the service-desk-comment-field component (see link above) and use standard Comment visibility which for all comments made by email will be empty)
https://ecosystem.atlassian.net/browse/ACJIRA-304 and https://ecosystem.atlassian.net/browse/ACJIRA-320 JEMHC cannot control what comments are created as (Public or Internal)
https://jira.atlassian.com/browse/JSD-1473 - JEMHC doesn't play well with mails from Portal users
https://jira.atlassian.com/browse/JSD-107 - JEMHC doesn't link to portal pages, will only link back to the issue URL, because there is no current JSD API to know what that is
Here is an example of the new theme notification:
If your JEMHC Notification > Issue configs used system default theme, switching themes is simple, just edit the entry and use the Theme Switcher field to update all Issue Event Templates.
If you have used customized Templates, you'll need to create a new TemplateSet in the JSD theme and migrate the content of what you have changed (remember that there have been some macro changes)
New Features and Improvements
JEMHC-300 Add a ServiceDesk theme (template +css +images)
JEMHC-314 Comment Visibility handling needed
JEMHC-327 Message Viewer. See an email's text or html body on screen
JEMHC-328 Need to be able to set the assignee on create
Bugs
JEMHC-331 Theme: Style tab doesn't refresh editor on first selection
JEMHC-323 Only validated SMTP addresses should be added to custom fields
JEMHC-324 email template typo
JEMHC-319 autoblackisting need to have a 'initializing' type message if not already done