Blog from July, 2017

JEMH 2.2.5 Release Notes

Attachment filtering on Project Mappings

As part of the migration of configuration, Project Mappings now have an Attachment Filters section.  Learn more about Attachment Filters.

Blacklisting images by URL

Sometimes emails are processed that contain "soft links" to images via URL.  A new blacklisting type has been added that can be used to remove these images from descriptions and comments.  Learn more about blacklisting images by URL.

Custom Field selection changes

Use of custom field ID's

Historically, most custom field selections in JEMH profiles were stored in the database by name.  This could cause problems as custom field names are subject to translations.  This meant that if an administrator had a different user profile language to one of the emailing JIRA users, custom fields would not be found and therefore not be populated on issues.

JEMH now properly handles custom field selections by their unique ID which should resolve this problem.

User interface changes

In order to improve the end user experience, almost every custom field selection is now made using fields that make it easy to search for the custom field you are looking for.  In a few places this replaces free-text fields - no more guessing required!

JEMH 2.2.1 Release Notes

Currently using 2.2.0?

If you upgraded to JEMH 2.2.0 you would have lost any labels that were set under Profile>Issue>Labels. If you have exported backups of your profiles prior to upgrading to 2.2.0, importing these in 2.2.1 will restore previous behaviour as part of the below migration process. Users who have not previously installed version 2.2.0 will have these labels migrated without having to re-import profiles.

Migration of profile level labels

The setting found at Profile>Issue>Labels allowed issue labels to be defined "globally" so that any issue created by JEMH would have those labels set, regardless of project.  This setting was removed in the previous release due to being deprecated.

In order to keep the ability to set "global" labels, a new setting has been added to each non-default project mapping.  The new setting allows configuration of whether labels from the default mapping are added or not.

Setting a mapping to inherit means that when the mapping is used, labels from the default project mapping will be set also.  Using the setting override will mean that only labels from the rule-matched mapping will be used.

Upgrading to 2.2.1 migrates legacy profile level labels (if present - see top of page) to the default project mapping.  At the same time, other non-default mappings are set to inherit the labels from the default mapping. If a profile is found not to have any legacy profile-level labels set, the project mappings will be set to override the labels on the default mapping.

Delegated Blacklisting

JIRA Project Administrators can now configure blacklisting specifically for their project via the JIRA Project Administration screen.

JEMH 2.2.0 Release Notes

Read before upgrading

Loss of profile level labels may occur by upgrading to version 2.2.0. If possible, it is recommended that customers should hold and upgrade to version 2.2.1 instead (once available).

If 2.2.0 must be installed in the meantime make sure that you have exported backups of your profiles before doing so, and consider re-importing once on version 2.2.1.

JIRA 7.4 compatibility

The JEMH 2.2.x series is intended for use with the JIRA 7.4.x series, and is marked as such on the Atlassian Marketplace.

Removal of deprecated features

JEMH-5838 - Getting issue details... STATUS

As per the above task, the following features have been deprecated since the 2.0.x series and are now removed as they have been superseded:

  • Profile>Workflow section has been removed.  A more flexible and user-friendly feature is available under Project Mappings since version 2.0.1
  • Profile>Issue>Label has been removed.  Project Mappings are to be used for issue label setting (important - see warning at the top of these release notes!)
  • Profile>Issue>IssueTypeProfile>Issue>PriorityProfile>Project>Fallback ProjectProfile>Project>Fallback Component and Profile>Project>Fallback IssueType settings have been removed as Project Mappings allow the same functionality but with greater flexibility.

Ad-hoc Notification fixes

Known Issues

  • Loss of profile level labels (see top warning)