You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

This condition checks the value of a field or a text composed of various custom fields against a regular expression.

Configuration

Value

Select how to retrieve the value that will be checked against the regular expression. You can choose between the following options:

OptionDescription
Value from fieldIf 
Manual valueSet value manually (parser expression), then enter plain text and optionally use field codes, e.g. %{issue.summary}, to insert field values that will be replaced at runtime.
Additional options

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

OptionDescription

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.


Use cases and examples


If you still have questions, feel free to refer to our support team.