Introduction
This post function allows you to set related issues field value on the basis of the same or another field value from the current issue or its parent. For example this post function can be used in the following scenarios:
- Update the subtasks resolution with the parent issue resolution
- Assign linked issues to the current user
- Update selected issues' due date to a day as in the current issue
| Element summary | |
|---|---|
| Status | CURRENT |
| Version compatibility | 6.0.1 - Latest |
| Supported | Yes |
| Introduced in version | 1.0.0 |
Post function parameters
This post function takes the following parameters:
- Issue relation and JQL - described at the bottom of the page
- Source Field - a list of JIRA standard and custom fields. This is the source of value.
- Destination Field - a field to be updated in related issues
- Add source value(s) to destination field - by ticking this option you will add missing options to the destination custom field (if it's dictionary-based) or append a source text to the existing destination field value.
- Copy to destination field - a condition to check on the destination field
- Always
- Only if empty
- Only if not empty
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 use
