Introduction
Validator that checks if related issues meet field-based criteria. Flexible JQL-based issue selection and number of options allow you to customize validation.
You can use this validator for (e.g.):
- Validating if all subtasks have given status
- Disallow transition if parent issue has more than 2 components
- Disallow transition if any subtask of 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 - described below
- Issue field - field to be used in comparison with related issues
- Compare type
You may select one of three 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. Which value - 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 - operator for comparison and enabling case sensitivity.
- Text value - desired value. For some fields it can be list of values.
- Multiple issue bahaviour - decide how to deal with if more than one issue is selected
- Failed validation message - Message for user if validation fails
- Evaluate value on - method of validation
- Original issue - issue without changes user made (on transition screen)
- Issue after transition - issue after changes made on transition screen (but it doesn't reflect changes made by post functions)
Working with related issues Related issues can be selected by using two inputs: Issue Relation - where you can choose a relation with the current (transitioned) issue; JQL - you can put your JQL text to filter some issues from the results. If you leave the JQL Field empty, all issues in a given relation are taken into account. In the example above you wanted to execute a workflow function on subtasks of the current issue and take additionally only the ones with the "Sub-task" and priority="High" type. In the JQL field you can put some text tags to be replaced with actual values of the current (transitioned) issue: $$CURRENT_DATETIME$$ $$ASSIGNEE$$ $$CURRENT_STATUS_CATEGORY$$ The JQL field has a built-in validation feature. If your query is incorrect, you will see a red sign next to the JQL field and an error description as shown below:
Tags
Tag Description The current date and time. $$CURRENT_USER$$ The name (login) of the current user. $$ISSUEKEY$$ The key of the current issue. $$ISSUEID$$ ID of the current issue. $$REPORTER$$ The current issue reporter's name. The current issue assignee's name $$PROJECTKEY$$ The project key. $$CURRENT_STATUS$$ The current issue status. $$ISSUETYPE$$ The issue type. $$CREATED_DATE$$ The date when the issue was created. A status category of the current issue (To Do, In Progress or Done). $$TRANSITION_NAME$$ The name of an actual transition (doesn't work in Conditions) $$TRANSITION_ID$$ ID of an actual transition (doesn't work in Conditions). $$TRANSITION_COMMENT$$ The content of a transition comment (doesn't work in Conditions). 
Example of usage
