A workflow post-function that sets the value(s) of a selected field with value(s) from the same/different field of an issue's parent issue.To add the 'Copy field value from parent issue' post function to a transition :
Click Edit for the workflow that has the transition you wish to add 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 parent issue
from the list of post-functions.Click on
Add
to add the post-function on the transition.Select the field from the
Field
drop-down.Select the destination field from the
Destination field
drop-down. See below for information on this option.Click on
Add
to add the post-function to the transition.After adding, move the post-function to the appropriate position according to Placing post-functions in a transition document.
See here for a case for this post-function
Known issues common to all post-functions:
Troubleshooting this post-function configuration: In case the post-function does not work as expected these are the things to look out for
JMWE shows an error message on the issue view if any error occurs during the execution of the post-function. This message is displayed only if the current user is a Jira administrator.
When you add this post-function to a transition and trigger the transition, the add-on sets the value(s) of the selected field to the value(s) from the same/different field of the issue's parent issue.
Options
Destination field: Allows copying to a different field than the source field. For example, automatically add the Reporter of the parent Epic to the Watchers of a User Story. Note that if the source field is read-only, you cannot select
Same as source field
in this option.
Copy only if not set: Copies the value of the selected field, only when the field is empty on the current issue.
Create missing value(s): Allows creating any missing Component/s or Version/s while setting or copying a field that expects Versions or Components. Note this is applicable for version and component fields.
Ignore empty value: Will not set (clear) the selected field of the current issue, if the value from the parent issue is empty or null.
Add parent value(s) to the current issue: Appends the selected field of the current issue with value(s) from the same/different field of its parent issue. This is applicable only to multi-valued fields.
Send notifications: JIRA sends notifications for the change in the selected field value on the current issue. You can control the default value of the
"Send notifications"
option in the Configuration page under JMWE administration. Click here for more information.
Conditional execution
To execute this post-function based on the result of a Nunjucks template see Conditional execution.
Run As
Run as current user: The current user will be the author of the field change.
Run as add-on user: The add-on user will be the author of the field change.
Run as this user: Any user selected in this field will be the author of the field change.
Running this post-function as any user other than the "Add-on user" is discouraged
If you select any option other than "Run as add-on user", so that the change appears to be done by the current user or a specific user, the following must be true:
The destination field must be present on the Edit screen applicable to the issue being modified
The selected user must have the Edit issues permission on the issue being modified
Delayed execution
Post functions are provided with an option to delay their execution. You need to select the number of seconds to wait until the post-function is run, a default of 1 sec to a maximum of 20 seconds.
Workflows that depend on post functions being executed in a specific order fail due to the asynchronous nature of the Connect post-functions in Jira Cloud. One of the workarounds is to delay the execution of the post-functions and thereby create a more predictable execution order. For example, on the approval of a Story you want to create sub-tasks and immediately transition them; in this case, you will have to delay the execution of the Transition Linked Issues post-function, so that the sub-tasks are created before they are transitioned. See the use case below.
It is recommended to use the Sequence of post-functions post-function or Shared Action post-function post-function to run a list of post-functions in a sequence instead of applying a delay.
Sample use cases for Delayed execution
On the creation of a Bug, assign it to a member of the QA team and then add the Assignee to the Watchers.
On the approval of a Story, create subtasks for Development and QA, and transition them to In Progress status.
The parent/child relationship in JIRA refers to Issues and their Subtasks, not to the Epics and their Stories.
If you wish to copy a field from an Epic to a Story, you can use the Copy field value from linked issues post-function.
Use case
A typical use case for this post-function is to set the value(s) of a selected field with value(s) from the same/different field of an issue's parent issue. Consider a use case where you want to copy the Fix Versions of the subtask from the parent. To configure this:
Add the Copy field value from parent issue post-function to the Create transition of the sub-task workflow.
Select
Fix Version/s
inSource Field
.Select
Same as source field
in theDestination field
.
Refer here for more use cases