The Fields required or changed validator checks if fields are set/empty or have/haven't changed on the transition screen.
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. | BEGINNER | |
| 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. | BEGINNER |
| 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. | BEGINNER | |
| 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. | BEGINNER |
If you still have questions, feel free to refer to our support team.
