Copy field value from related issues (Deprecated)
This post-function has been deprecated and replaced by Copy field value. It could be removed at any time. You can still use it, but it is highly recommended that you update any workflows that use this post-function.
A workflow post-function that sets the value of a field to the value of a field in related issues (such as linked issues, Stories of an Epic, Epic of a Story, subtasks of an issue, issues returned by a Groovy script or a JQL search, etc.)
When you add this post-function to a transition and trigger the transition, the add-on sets the value of the "Destination field" on the current issue to the value of the "Source field" in the related issues.
This post-function does not work with remote links (links to Jira issues residing on another Jira instance/server).
JMWE now considers "symmetrical" link types (such as "relates to") as one link direction instead of two on the configuration screens and in the post-function execution.Â
To add the 'Copy field value from related issues' post-function to a transition:
ClickÂ
EditÂ
for the workflow that has the transition you wish to configure the post-function on.In the Workflow Designer, select the transition.
Click onÂ
Post FunctionsÂ
in the properties panel.Click onÂ
Add
Âpost function
.SelectÂ
Copy field value from related issues
 from the list of post-functions.Click onÂ
Add
 to add the post-function on the transition.Select the field from the source field from theÂ
Source Field
drop-down.Select the field from the destination field from theÂ
Destination Field
drop-down. Select "Same as Source field
" to copy it to the same field.Select the issues to operate on fromÂ
Source issue(s)
 fieldSelect the options provided to add the required parameters.
Click on
Add
to add the post-function to the transition.
Note that you need to publish the workflow for the new post-function to take effect.
Source issue(s)
Select the issues to copy from. They can be:
Linked issues: Select issue(s) linked to the current issue through any link type or a specific link type such as
blocks
,is cloned by
, etc.Sub-tasks of the current issue: Select this option to operate on the sub-tasks of the current issue
Parent issue of the current sub-task: Select this option to operate on the parent of the current issue
Issues that belong to the current Epic: Select this option to operate on the issues that belong to the current Epic
Epic of the current issue: Select this option to operate on the Epic of the current issue
Child issues of the current issue in the Portfolio hierarchy: Select this option to operate on the child issues of the current issue in the Portfolio hierarchy
Parent issue of the current issue in the Portfolio hierarchy: Select this option to operate on the parent issue of the current issue in the Portfolio hierarchy
Issues returned by a Groovy script:Â Â Input a Groovy script that returns either a single Issue object, or a Collection of Issue objects, or a String representing the key of an issue, or a Collection of Strings each representing an issue key. For example:
"TEST-1"
["TEST-1","TEST-2"]
ComponentAccessor.issueManager.getIssueObject("TEST-1")
[ComponentAccessor.issueManager.getIssueObject("TEST-1"),ComponentAccessor.issueManager.getIssueObject("TEST-2")]
issue.parentObject
issue.getLinkedIssues()
Issues returned by a JQL search: Â Input a JQL search expression, including an optional Groovy Template markup. For example:
project = TEST
returns issues of the project with the key TESTproject = ${issue.get("project").key} and assignee = ${
currentUser.name}
returns issues of the project the current issue belongs to and assigned to the current user.To operate on issues of a project with key
TEST
and issue type name same as the value in a text field<% if (issue.get("Single line text")) { %> project = TEST and issuetype = ${issue.get("Single line text")} <% } else { %> issuekey=INVALID-1 <% } %>
Â
OptionsÂ
Copy only if not set
Sets the value(s) of the selected field of the current issue, only when the field is empty on the current issue.
Ignore empty values
Will not set (clear) the selected field of the current issue, if the value from the related issues is empty or null.
Add source value(s) to destination field
Appends value(s) from the field of each related issue to the selected field of the current issue. This is applicable only to multi-valued fields.
Create missing value(s)
Allows automatically creating any missing value(s) while copying values that do not exist in the destination issue's project and hence should be created from the source issue's project. This is applicable only to Affects Version/s, Fix Version/s, Single version and Multi-version picker type custom fields, Components, Radio buttons, Checkboxes, Single select and Multi-select list type custom fields.
Conditional execution
Error Handling
Â