JEMH 4.0.0
JEMH 4.0.0 is finally out for Jira 9.0.0!
This release took a while…
This release took longer than usual to complete due to some undocumented changes in Jira 9.0.0 (velocity template usage of Active Objects no longer work) that broke pretty much every single UI screen’s in JEMH, fixing that let us to address other things in our backlog that will make a big impact for customers, primarily:
Profiles are now fully cached in memory which now drives both UI Profile navigation which becomes much snappier, as well as email processing where the interaction with the db to retrieve configuration will be near zero. Its DC aware and will have its local cache replicated to other nodes within 1 minute of noticed changes.
Breaking changes
As a Major release, we have taken some steps to clean house that result in breaking changes:
JEMH Profile XML exports from < 4.0.0 cannot be imported into JEMH 4.x, JEMH 4+ profiles are:
<Profile version="11">
We have removed historic support for simple ‘username’ for fields such as the default reporter, in favour of the expanded form:
<user displayName="admin" emailAddress="admin@admin.com" key="JIRAUSER11000" name="admin"/>
that has been included in the JEMH 3.3.x series of releasesWufoo field processor has been removed due to lack of use/duplication
3rd party Field Processors access to configuration is now through dedicated data carrier ‘bean’ classes in the API package, see Javadoc for IJEMHRuntimeConfig
Changelog
JEMH-8053 08/Jul/22 RESOLVED Allow Privileged user to be cleared in Notification Config
JEMH-8043 07/Jul/22 IN PROGRESS Project Mappings Domain Rules can have the same name
JEMH-8030 28/Jun/22 RESOLVED Setting parentIssueKey in Script Field Processor result map leads to Forward outcome & notification
JEMH-8026 24/Jun/22 RESOLVED Profile import: add outcome dialog to notify user that project Mappings without a project will not be imported
JEMH-8019 15/Jun/22 RESOLVED Configuration Advisories need grouping
JEMH-8017 14/Jun/22 RESOLVED PNG thumbnail attachments are given JPEG ext and ContentType.
JEMH-8016 10/Jun/22 RESOLVED Project Mapping > WorkflowRules - RUN_WHEN_ISSUE_TYPES Missing from XML export beans, missing from Copy command
JEMH-8015 10/Jun/22 RESOLVED Failure to test a line length when processing email headers
JEMH-8013 06/Jun/22 RESOLVED Customer notification is not rendered if no 'Standard' template is selected
JEMH-8011 02/Jun/22 RESOLVED Profile > email > html > Heading level not stored in beans
JEMH-8010 01/Jun/22 RESOLVED remove deprecated setMakeCustCommentsPublic/isMakeCustCommentsPublic from config
JEMH-8009 01/Jun/22 RESOLVED JEMHConfigEntity.isEscapeWIkiMarkup should be removed
JEMH-8008 01/Jun/22 RESOLVED Profile > Email > HTML > Em tag handling missing from XML export
JEMH-8007 01/Jun/22 RESOLVED Autolabel config > isCanCreate missing from XML export
JEMH-8006 01/Jun/22 RESOLVED UserCreateTmplId missing from XML export
JEMH-8005 01/Jun/22 RESOLVED userSignupTemplate missing from XML export
JEMH-8004 01/Jun/22 RESOLVED nonRenamedAtts field missing from XML export
JEMH-7996 27/May/22 RESOLVED LDAP > item > Preferred User Directory & DlAddressRegexp fields not saved in XML
JEMH-7994 27/May/22 RESOLVED Profile > User > CreateUserEmailCondition not set in profile xml
JEMH-7992 27/May/22 RESOLVED Profile > Security > isTreatUnprivilegedAsNonJira not saved in Profile XML
JEMH-7991 27/May/22 RESOLVED Profile > Directives > UseTranslatedFieldNames not included in profile export/import
JEMH-7939 24/Mar/22 RESOLVED Post-function Address CFs deselected during edit if not using 'Default' CF types
JEMH-7826 03/Nov/21 RESOLVED Display Single Group custom fields by default on Post Funciton config screen
Additional Improvements
Profile Breadcrumb trail: has become more consistent, more links added allowing new tabs to be opened ‘deeper’ into Project Mappings and below.
Advisories: We’ve seen some monster profiles through support that showed up a lot of advisories, impacting the usability of the main configuration view, so we’ve moved them into their own Advisories section. Individual project mappings now have there project-specific advisories made visible
Upgrade path
Customers must upgrade through Jira 8.x and latest available JEMH 3.3.10x before upgrading to Jira 9.0+