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
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
📚 Use cases and examples
| Use case | JWT feature | Workflow function | Use case description | Complexity |
|---|---|---|---|---|
| Check for at least one component |
|
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 |
|
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 |
|
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. |
