This validator checks if fields are set/empty or have/haven't changed on the transition screen.
Select the field to be checked, and in a subsequent step the desired behavior. The following options are available:
|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.
|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.
If the transition is triggered by a JWT post function, e.g. through Transition issue, the validation will be skipped.
If the transition is triggered by a bulk operation, the validation will be skipped.
If the create transition is triggered by a clone operation, the validation will be skipped.
f the create transition is triggered by a mail handler, the validation will be skipped.
You have the following options:
Define where the error message should be displayed. By default, the message will be shown at the top of the transition screen, or in case there is no transition screen, as a popup.
Alternatively, you can locate the message below any other field. This option only makes sense, if there is a transition screen defined for the specific transition.
Due to limitations in Jira Service Management, the location parameter will be ignored on Jira Service Management related screens. The location parameter only works for the Create Issue transition screen if JSD version 4.10 or higher is being used.
In comparison to e.g. our calculated custom fields it is not possible to display HTML here. Displaying links to specific issues, for example, is not possible inside the error message.
After clicking on the Add translation button you can optionally translate the error message to other languages.
The language in which the error message will be displayed depends on the language setting of the individual users.
If you want to use this functionality in a condition instead, have a look at the following condition: Fields required