Validation based on regular expression

Choose between the two following options:

Enter plain text and optionally use Field codes, e.g. %{issue.summary}, to insert field values.

Choose from one of the following options (multi-choice is possible):

Case insensitive - Case insensitive matching is done in a manner consistent with the Unicode Standard.

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

Dot all - Expression . matches any character, including a line terminator. By default, this expression does not match line terminators.

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

Negate condition - 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):

• Skip validation for JWT post functions - If the transition is triggered by a JWT post function, the validation will be skipped.
• Skip validation for bulk operations - If the transition is triggered by a bulk operation, the validation will be skipped.
• Skip validation for clone operations - If the create transition is triggered by a clone operation, the validation will be skipped.
• Skip validation for mail handlers - 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.

Add translation