...
These Directives must be specifically enabled (e.g. Profile > Directives > Directive Processing Behaviour : Create/Comment).
...
Translating directives
Where keys and values do not match Jira custom fields or appropriate values, JEMH Aliases allow a) complete key+value conversion into different key+values, b) key replacement, b) value replacement, this feature allows translation of external values into 'internal' values suitable for use.
...
Directives require no specific Jira permission, but the user under which an activity is performed needs have appropriate permissions. Fo For example, adding email CC header participants as watchers of that issue will require “Manage watchers” permission.
It is possible to limit what users can do with Directives by setting a whitelist, perhaps just with 'priority' or even specific Alias keys that have been defined. Directives can be limited by whitelist Allowlist or blacklistBlocklist, using both is a little nonsensical, but will mean within the set of whitelisted Allowlisted directives. Those that are blacklisted Blocklisted are then discounted.
...
Parsing and outcome for content
...
The tools are available to help you solve these problems yourself (faster). If you cannot do so, raise a support case, including:
Your Profile XML (there is an export operation on the Profile list page for each profile)
The email content from the JEMH Audit History or Test Case, attached as a file NOT PASTED!
| Warning |
|---|
.msg files from Outlook are not usable in any way and will be deleted on upload. |
...