Introduction
Excerpt Include Universal user-based condition Universal user-based condition nopanel true
It's a validator that checks if related issues meet the field-based criteria. A flexible JQL-based issue selection and a number of options allow you to customize the validation.
You can use this validator to e.g.:
- Validate whether all subtasks have a given status.
- Disallow a transition if the parent issue has more than 2 components.
- Disallow a transition if any subtask of the current issue is not assigned.
| Element summary | |
|---|---|
| Status | CURRENT |
| Version campatibility | 6.0.1 - Latest |
| Supported | Yes |
| Introduced in version | 1.0.0 |
Validator parameters
- Related Issues - as described below.
- Issue field - a field to be used in comparison with related issues.
- Compare type.
You may select one of three comparison methods.
Option Description Compare Field Value It compares the value of a selected field. If the field contains more than one option (e.g. a multi-select type field) all options are listed as a comma-separated text. Regular expression It allows you to compare the field value (the same as above) with a regular expression. Number of elements It returns the number of elements in the field. If the field is a simple text or a number, it returns 1 (if the field is not empty). For multi-option enabled fields, the number of elements will be returned. An Eempty empty field is always a zero. Which value - this option allows you to choose which value will be used in the comparison.
- Current Value.
- Previous value (the last one).
- Any historical value (excluding the current value).
- Operator & case sensitivity - you can choose the operator for comparison and enable case sensitivity.
- Text value - the desired value. For some fields it can be a list of values.
- Multiple issue bahaviour - decide how to deal with if more than one issue is selected
- Failed validation message - a message is sent to the user if the validation fails.
- Evaluate value on - a method of validation.
- Original issue - an issue without changes made by the user (on the transition screen).
- Issue after transition - an issue after changes made on the transition screen (but it doesn't reflect changes made by post functions).
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
Example of use
