...
Script Field Processor or Script Project Mapping Rules are not yet available. This is a important feature and is something we hope to offer between Q4 '21 - Q1 '22.
https://thepluginpeople.atlassian.net/browse/
Jira Legacy server System JIRA serverId 31e1f342-5dce-3979-a43c-85899d565476 key JEMHC-2171
What's different?
Data Storage
...
| Info |
|---|
For background, see How Jira events turn into emails and Manipulate Webhook webhook data in a Templatenotification templates. |
Your Jira Cloud instance will send event data to JEMHC when changes are made to issues. JEMHC will only retain webhooks for processing where you have configured JEMHC to generate notifications for specific projects, in this way, we retain only the subset required for JEMHC to do what you have configured.
...
We don’t support migrating audit history from JEMH Server/DC to JEMHC as JEMH Server is able to retain unlimited volumes of data. In JEMHC (with customer opt-out) we can store the most recent 100 inbound and outbound messages for your diagnostic purposes.
Issue Association
Foreign Key Issue Association configuration in JEMHC is different due to the structure of the Profile.
In short, JEMHC restricts Issue Association in a Project Mapping, scoping to the mappings selected Project.
However, the default Project Mapping will not scope to the mappings selected Project, but any non-default mappings added that inherit the Foreign Key Issue Association will scope to the non-default mappings selected Project.
For further information, see https://thepluginpeople.atlassian.net/wiki/spaces/JEMHC/pages/72908873/Understand+how+Issue+association+works#Regexp-foreign-key-association