This function has been renamed with the JWT 3.0 release. Find the new documentation at: |
Condition based on regular expression and Validation based on regular expression are two forms of a same feature for checking the value of a field or a text composed by various custom fields against a regular expression.
In this example we show a configuration for validating the US state code entered in a custom field called "State":
Regular expression used is: ^((AL)|(AK)|(AS)|(AZ)|(AR)|(CA)|(CO)|(CT)|(DE)|(DC)|(FM)|(FL)|(GA)|(GU)|(HI)|(ID)|(IL)|(IN)|(IA)|(KS)|(KY)|(LA)|(ME)|(MH)|(MD)|(MA)|(MI)|(MN)|(MS)|(MO)|(MT)|(NE)|(NV)|(NH)|(NJ)|(NM)|(NY)|(NC)|(ND)|(MP)|(OH)|(OK)|(OR)|(PW)|(PA)|(PR)|(RI)|(SC)|(SD)|(TN)|(TX)|(UT)|(VT)|(VI)|(VA)|(WA)|(WV)|(WI)|(WY))$
Once configured, the validation will look like this:
We will explain in detail each of the configuration parameters of these features.
These are two alternative parameters, i.e., only one of these parameters is used in each configuration at the same time.
Field codes have the following formats:
Multi-Level Cascading Select custom fields are also supported. For these fields values higher 1 can be used for index i.
Field codes can be checked up in a dropdown list available in the configuration screen of these features.
This is the regular expression that will be used for validating the value of the selected field or parsed text entered.
JAVA regular expression syntax is used.
Field codes with formats %{nnnnn} and %{nnnnn.i} can be inserted. Regular expression will be preprocessed before being evaluated, in order to replace each field code with its corresponding value. This way, dynamic regular expressions that depend on the value of fields in current issue, can be entered.
The way regular expressions are evaluated can be modulated with the following modes:
When this option is checked, not matching the regular expression is the requirement set for field value or parsed text, instead of matching it.
This parameter is only available in the validator form of this feature. It's a custom message to explain the user the cause that is preventing him from executing the transition.
Translations* to every language installed in the JIRA instance can be optionally entered.
In Condition based on regular expression the transition is simply hidden whenever condition isn't satisfied, so this parameter is not present.