...
Directives allow emails to direct JEMH on what issue attributes should be used during issue creation or update. Along with Project Mappings, they are one of the main ways to ensure that Jira is given all the information it requires to perform issue creation or modification.
...
Directive key | Example using At Prefix Field Processor (in email body) | Example using Subject Field Processor (in subject) |
|---|---|---|
Name or ID of field e.g. |
|
|
Using Directives with different Custom Field Types
...
Field Type
...
Description
...
Example using At Prefix Field Processor (in email body)
...
Checkbox
...
The value that is being set must already exist as an option within the Custom Field Configuration. If the value is not found it will result in the Custom Field not being updated.
...
When using different field types you must follow the supported format as if a different format is used it will mean that JEMH will not be able to set the value within the Custom Field.
Below are some examples using the At(@) Prefix Field Processor. For more info the At(@) Prefix Field Processor see: JEMH Mail Field Processors
Field Type | Additional information | Example using At Prefix Field Processor (in email body) |
|---|---|---|
Checkboxes | Value must already exist as an option within the Custom Field Configuration. |
|
Date Picker | Dates must follow the |
|
Date Time Picker | Date Time values must follow the |
|
Labels | Value does not have to already exist as JEMH can create new labels. |
|
Number Field | Largest value is 100000000000000 |
|
Radio Buttons | Value must already exist as an option with the Custom Field Configuration. |
|
Select List (cascading) | Value must already exist as an option with the Custom Field Configuration. |
|
Select List (Multiple Choice) | Value must already exist as an option |
|
Text Field (multi-line) | Multiple line values can be used with this Custom Field. |
|
Text Field (single line) |
| |
URL Field |
| |
User Picker (single user) |
|
| Note |
|---|
Note that from JEMH 2.5.1 date values supplied by email directives are locale sensitive. This means that for example, a Jira user who's profile is set to Spanish should send date values such as Prior to 2.5.1, date values should be sent using the system default locale. |
...