The Fields required condition of JWT DC is also available for JWT Cloud.
Since JWT DC field codes are not available in conditions or validators in JWT Cloud, they have to be replaced by their Jira expression equivalent.
Migration steps
Reconfigure the post function with the help of the following list, providing the necessary basics.
Migration details
Field parameter
The following list presents the fields supported by the Fields required condition in JWT Cloud. Fields not appearing in this list, cannot be mapped to JWT Cloud. All fields are available for the contexts "issue" and "parent".
|
|
|---|---|
| Affects version/s | |
| Assignee | |
| Attachments | |
| Issue links | |
| Subtasks | |
All custom field types | All custom field types provided on JWT DC side except Text Field (read-only) |
Both JWT DC and JWT Cloud allow to select a field out of the list and select the condition out of the following options:
Option | Description |
|---|---|
| is required | The specified field must have a value. If no value is present, the condition will fail. |
| must be empty | The specified field must not have a value. If a value is present, the condition will fail. |
The option "All options required" is not available in JWT Cloud. This concerns fields like Checkboxes, User picker (multiple users), or Select list (multiple choices).
Due to the different architecture, it may happen that the condition gets too complex. This is the case when many fields are checked. The condition cannot be saved, and a corresponding error message will be displayed. If that's the case, the condition has to be split up into two or more.
If you still have questions, feel free to refer to our support team.
