This validator checks the value of a field or a text composed of various custom fields against a regular expression.
Configuration
Choose between the two following options:
Select a specific field for the available list.
Enter plain text and optionally use Field codes, e.g. %{issue.summary}, to insert field values.
Test your expression by clicking the run button on the top right of the expression box.
Enter plain text and optionally use Field codes, e.g. %{issue.summary}, to insert field values.
Test your expression by clicking the run button on the top right of the expression box.
Choose from one of the following options (multi-choice is possible):
Case insensitive matching is done in a manner consistent with the Unicode Standard.
Expressions ^ and $ match just after or just before, respectively, a line terminator or the end of the input sequence. By default, these expressions only match at the beginning and the end of the entire input sequence.
Expression . matches any character, including a line terminator. By default, this expression does not match line terminators.
Input string is treated as a sequence of literal characters. Metacharacters or escape sequences in the input sequence will be given no special meaning. Case insensitive mode retains its impact on matching when used in conjunction with this mode.
When this option is checked, validation will be satisfied if the regular expression is NOT MATCHED by the selected field or entered parsed text.
Choose from one of the following options (multi-choice is possible):
- 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.
- If 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.
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.
Use cases and examples
Title |
---|
No content found. |
If you still have questions, feel free to refer to our support team.