JEMH 2.2.1 Release Notes

Created by Mike Harrison
Last updated: Jul 13, 2017
2 min read

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.