Fields required or changed | Decadis App Help Center

This validator checks if fields are set/empty or have/haven't changed on the transition screen.

⚒️ Configuration

Fields

Select the field to be checked, and in a subsequent step the desired behavior. The following options are available:

Option	Description
is required	The specified field must have a value. If no value is present, the validation will fail. false< ac:schema-version="1" ac:macro-id="4e70c8ef-3a70-4e23-ade7-1ede3f250dcf">info Please note that due to Jira expression restrictions, at most ten custom or comment fields can be validated with this option.
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.

You can select all Field codes which have Jira expression field code via the field code injector.

Error message

Enter the message to show to the end-user when the validation fails. If you don't enter a message, the default error Message for JWT for Jira Cloud "Validation failed for validator 'Fields required or changed (JWT)'" is displayed in case the validation fails.

If you want to use this functionality in a condition instead, have a look at the following condition: Fields required

📚 Use cases and examples

Use case	Workflow function	Use case description
Check for at least one component	Fields required Fields required or changed	Require a at least one component. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.
Make a fix version required and add a comment	Fields required or changed	Require a fix version and add a comment. This use case is valid for validators.
Make the assignee required	Fields required Fields required or changed	Require a non empty assignee. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.
Resolution must be empty	Fields required Fields required or changed	Not allow a resolution to be set. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator.