Introduction
Universal Issue Field Value Validator allows JIRA workflow developer to control field changes in flexible way. This validator can play role of
compare an user property value with a fixed value or field value. This powerful mechanism lets you validate workflow transition in flexible way. You can validate almost everything using one simple validator.
It operates on all JIRA standard and custom fields and compares them using field value, regular expressions, number of elements and field change on transition
For example you can build following conditions using our solution:
- Summary contains text "error"
- Assignee was (wherever in history) john.doe
- Assignee is not empty
- A Field is required
- Assignee was changed on transition screen
- At least 2 components have to be selected
- Issue has no more than 2 attachments
- At least 1 document in MS Word format (*.docx) is attached to issue (before current transition)
- Description previously contained some text
| Element summary | |
|---|---|
| Status | CURRENT |
| Version compatibility | 6.0.1 - Latest |
| Supported | Yes |
| Introduced in version | 1.0.0 |
Condition parameters
Select field
List of all JIRA (standard and custom) issue fields, project attributes, and some extra issue attributes like Attachments and number of worklogs.
There are some limitations when you're using some specific values
| Field | Restrictions |
|---|---|
| Attachments | If selected "number of elements", provides number of files attached to issue. If regular expression or field value option is selected, attachment names are processed (comma separated if more than one). This field must NOT be used with previous or historical value comparison and doesn't work with "Field was changed on transition" method. |
| Number of worklogs | Always provides number of entries in issue's worklogs, regardless comparison method you selected. This field must NOT be used with previous or historical value comparison and doesn't work with "Field was changed on transition" method. |
Current User | Contains login of current user This field must NOT be used with previous or historical value comparison and doesn't work with "Field was changed on transition" method. |
| Project name | Current project name. This field must NOT be used with previous or historical value comparison and doesn't work with "Field was changed on transition" method. |
| Project key | Current project key. This field must NOT be used with previous or historical value comparison and doesn't work with "Field was changed on transition" method. |
| Project category | Current project category name. This field must NOT be used with previous or historical value comparison and doesn't work with "Field was changed on transition" method. |
Compare type
You may select one of four comparison method:
| Option | Description |
|---|---|
| Compare Field Value | Compares value of selected field. If the field contain more than one option (e.g. multi-select type field) all options are listed as comma separated text. |
| Regular expression | Allows you to compare field value (same as above) with a regular expression |
| Number of elements | Returns number of elements in the field. If the field is simple text or number it returns 1 (if field is not empty). For multi-option enabled fields, number of elements will be returned. Empty field always is zero. |
| Field was changed on transition | Allows you to check in a field was changed, set or unset on transition screen. |
Which value (optional)
This option allows you to choose which value will be used in comparison
- Current Value
- Previous value (last one)
- Any historical value (excluding current value)
Operator & Case sensitive (optional)
Operator for comparison and enabling case sensitivity.
Text value or expected behaviour
Desired value. For some fields it can be list of values. For "Field was changed on transition" type it contains list of expected behaviours.
Example of usage
