Migrate 'Fields required or changed'

The Fields required or changed validator 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

  1. Add a Fields required or changed validator.

  2. Reconfigure the validator 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 or changed validator 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".

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 validation will fail.

must be empty

The specified field must not have a value. If a

value is present, the validation will fail.

must be changed

The specified field must have been updated during the transition / on the transition screen.

must not be changed

The specified field must not have been updated during the transition / on the transition screen.


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. 

Validation options

This parameter is not available in JWT Cloud. 

Error message

In JWT Cloud, only a fixed text without field codes or translations is supported.