This validator checks if fields are set/empty or have/have not changed on the transition screen.
Configuration
Use cases and examples
Title |
---|
No content found. |
If you still have questions, feel free to refer to our support team.
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 7 Next »
This validator checks if fields are set/empty or have/have not changed on the transition screen.
Define the fields to be validated then choose from the following options whether the Validation:
Choose from one of the following options (multi-choice is possible):
Option | Description |
---|---|
If the transition is triggered by a JWT post function, 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. |
Add an optional error message to show when validation fails.
Define where the error message should be displayed.
For the message content to be displayed when an error occurs, enter plain text and optionally use Field codes, e.g. %{issue.summary}, to insert field values.
Test your expression by clicking the play button on the top right of the expression box.
Click on the Add translation button and choose the desired language to be translated to.
Translations will be displayed based on the user's language setting.
Title |
---|
No content found. |
If you still have questions, feel free to refer to our support team.
Powered by Atlassian Confluence 8.5.15, themed by Refined 7.6.0 and Decadis AG