Fields required | Decadis App Help Center

This condition ensures that one or multiple fields either have a value or are empty in order to execute a transition.

For cascading select list fields, both levels are considered and need to have/not have a value.

🛠️ Configuration

Notes

You can optionally enter a short Note (limited to 80 chars) and a longer Explanation (limited to 500 chars) to summarize what you are using the function for. This can help you differentiate multiple functions of the same kind in a single transition, as the Note will be shown in the workflow transition view.

Fields

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

Option	Description
is required	The specified field must have a value. If no value is present, the condition will fail. 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 condition will fail.

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

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

Conditional Execution

You can optionally specify a Jira expression to define the circumstances (or conditions) under which the condition should be applied.

The result of the Jira expression must return a boolean value of either:

true → the condition will be applied
false → the condition will be ignored (i.e. the transition will be available)

Pro Tip: Use this e.g. to allow Administrators or App/Automation users to bypass normal process restrictions.

📚 Use cases

Use case	Workflow function	Use case description
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.
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 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.

Use case

Workflow function

Use case description

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.

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 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.