Copy field value to linked issues

This post-function is obsolete. While you may continue using this post function, which will not be removed from JMWE, we recommend you use the more powerful Copy issue fields instead for new automations.

To add 'Copy field value to linked issues' post-function to a transition : 

  1. Click Edit for the workflow that has the transition you wish to add the post-function on.

  2. In the Workflow Designer, select the transition.

  3. Click on Post Functions in the properties panel.

  4. Click on Add post function.

  5. Select Copy field value to linked issues from the list of post-functions.

  6. Click on Add to add the post-function on the transition.

  7. Select the field from the Field drop-down.

  8. Select the destination field from the Destination field drop-down. See below for information on this option.

  9. Select the link type from the Issue Link Type drop-down.

  10. Click on Add to add the post-function to the transition.

  11. After adding, move the post-function to the appropriate position according to Placing post-functions in a transition document.

See here for a use case of the 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 copies the value(s) of the selected field into the same field of all issues linked to the current issue through the selected link type.

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 all the linked issues, only when the field is empty on the linked issue(s).

  • 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 linked issues, if the value from the current issue is empty or null.

  • Add value(s) to the linked issue: Appends the value(s) of the selected field to the same/different field of all the linked issues. This is applicable only to multi-valued fields.

  • Send notifications: JIRA sends notifications for the change in the selected field value on all the linked issues. 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

Note that you can use this function to copy a field to

  • A parent issue of a sub-task by using the built-in is Subtask of link type and vice versa using the is Parent of link type

  • The Epic of an issue by using the built-in belongs to Epic link type and vice-versa using the is Epic of link type


Use case

A typical use case for this post-function is to copy a field value to issues linked to the current issue during a transition. Consider a workflow where you want to copy the Fix Version/s field from the Stories to Epic, after resolving a user story.

  • Add the Copy field value to linked issues post-function to the Resolve transition of the Story workflow.

  • Choose the has Epic link type.

  • Select Fix Version/s in Source Field.

  • Select Same as source field in the Destination field.

  • Check Add value(s) to the linked issue option.

See here for more use cases