| Excerpt |
|---|
A workflow post-function that copies the value(s) of a selected field to the same/different field of the issue's parent issue. |
To add 'Copy field value to 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 FunctionsClick on
Addpost function.Select
Copy field value to parent issuefrom the list of post-functions.Click on
Addto add the post-function on the transition.
5.png?version=1&modificationDate=1493621143567&cacheVersion=1&api=v2&width=500){kind=spacer}
5.png?version=1&modificationDate=1493621143567&cacheVersion=1&api=v2&width=265)
Select the field from the
Fielddrop-down.Select the destination field from the
Destination fielddrop-down. See below for information on this option.After adding, move the post-function to the appropriate position according to Placing post-functions in a transition document.
Here are a few Use cases for this post-function.
Known issues common to all post-functions:
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
Troubleshooting this post-function configuration: In case the post-function does not work as expected these are the things to look out for
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
When you add this post-function to a transition and trigger the transition, the add-on copies the value(s) of the selected field to 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(s) of the selected field into the same/
different field of the issue's parent issue, only when the field is empty on the parent 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 parent issue, if the value from the current issue is empty or null.
Add subtask's value(s) to the parent issue
Appends the value(s) of the selected field to the same/
different field of the issue's 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 parent 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.
| Note |
|---|
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:
|
Delayed execution
To delay the execution of this post-function see Delayed execution.
| Info |
|---|
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 a Story to an Epic, you should use the Copy field value to linked issues post-function. |