...
JEMHC can’t use the built-in mailbox address provided by Atlassian, so you must use an external one. When doing so you may need allow connections from the JEMHC public IP address to to your mail service. For finer grained access control, you could setup dedicated certificates that only your configuration has.
What
...
Scripting support
Script Field Processor or Script Project Mapping Rules are expected to be released by end AUG 2023. This is a important feature and is something we have implemented and is in a closed beta right now, we expect this to be public by end AUG 2023, functionality includes:
JS PreProc Task (header manipulation)
JS Script Field Processor
JS Script Rule support in Project Mappings
JS Custom Field Default
What's different?
Data Storage
...
The structure of the JEMH Profile is very different from JEMHC. JEMH Profiles still have a lot of top-level configuration whereas JEMHC was designed with lessons-learned from JEMH whereby Project Mappings in JEMHC are Profile top-level feature, containing the majority of all configuration, Rules also then provide a subset of the Project Mappings.
Scripting support
Scripting support in JEMHC exists for:
Javascript PreProc Task (header manipulation)
Javascript Script Field Processor
Javascript Script Rule support in Project Mappings
Javascript Custom Field Default
The multi-tennant nature means that security is always at the forefront, and for that reason, scripts are restricted in what they can do, effectively they have access to the ‘issue' JSON structure, and the mail content where applicable, there are no remote calls allowed and no special custom functionality beyond javascript default scripting.
Messaging
Inbound/Outbound mail server connectivity isn’t within JEMH for Server/DC, in JEMHC, we have re-implemented all inbound/outbound mail server connectivity functionality. For example, JEMHC has OAuth authorization support, which requires specific admin actions to support, that cannot be migrated.
...