This validator 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:
|
Option |
Description |
|---|---|
|
Value from field |
If you select this option, you can select a specific field in a subsequent step. The value of this field will be evaluated against the regular expression. |
|
Set value manually (parser expression) |
You can enter the text to be evaluated against the regular expression using an expression in Basic text mode. Learn more about the possibilities of the JWT expression editor. |
Regular expression
Enter plain text representing a valid regular expression and optionally use field codes to insert field values. The expression will be used to match the substring in the selected target field.
Additional options
Choose one of the following additional options to further refine how to evaluate the value against the regular expression.
|
Option |
Description |
|---|---|
|
Case insensitive |
The evaluation will ignore the case of the input value |
|
Multiline |
Characters ^ and $ match just after or just before, respectively, a line terminator or the end of the input sequence. By default, these characters only match at the beginning and the end of the entire input sequence. |
|
Dot all |
"." matches any character, including a line terminator. By default, this character 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 |
The condition will be met if the provided regular expression does not match. |
Validation options
The validation can be skipped under certain circumstances Select one or multiple scenarios in which you want to skip the validation to ensure the correct execution of certain operations.
|
Option |
Description |
|---|---|
|
Skip validation for JWT post functions |
If the transition is triggered by a JWT post function, e.g. through Transition issue, 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. |
Error message
You can optionally define a custom error message in case the validator fails, which will be shown to the user trying to execute the transition.
You have the following options:
Location
Define where the error message should be displayed. By default, the message will be shown at the top of the transition screen, or in case there is no transition screen, as a popup.
Alternatively, you can locate the message below any other field. This option only makes sense, if there is a transition screen defined for the specific transition.
Due to limitations in Jira Service Management, the location parameter will be ignored on Jira Service Management related screens. The location parameter only works for the Create Issue transition screen if JSD version 4.10 or higher is being used.
Message
Define the content of the error message in Basic text mode or Advanced text mode.
Learn more about the possibilities of the JWT expression editor.
In comparison to e.g. our calculated custom fields it is not possible to display HTML here. Displaying links to specific issues, for example, is not possible inside the error message.
Translations
After clicking on the Add translation button you can optionally translate the error message to other languages.
The language in which the error message will be displayed depends on the language setting of the individual users.
If you want to use this functionality in a condition instead, have a look at the Condition based on regular expression.
📚 Use cases and examples
| Use case | JWT feature | Workflow function | Parser functions | Label |
|---|---|---|---|---|
| Prevent users from selecting specific fix versions |
|
|
