- Related Issues - as described below.
- Field - a field to be compared with the current issue.
- Operator - a math operator to be used.
- Target value - the desired number of related issues to pass the condition.
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:
|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).|
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: