Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email support@appfire.com

Copy field value from linked issues

Owned by Radhika Vijji. (Unlicensed)

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.

A workflow post-function that sets the value(s) of a selected field to the value(s) from the same/different field of an issue linked to the current issue through a selected link type.

To add the 'Copy field value from 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 from 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 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.

Known issue 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 a selected field to the value(s) from the same/different field of issue(s) linked to the current issue through the selected link type.

When there is more than one linked issue, by default the value will be copied from one (random) linked issue. But when the Add value(s) to the issue option is selected, value(s) from all the linked issues will be appended to the current 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: Sets the value(s) of the selected field of the current issue, 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 values: Will not set (clear) the selected field of the current issue, if the value from the linked issues is empty or null.

  • Add value(s) to the issue: Appends value(s) from the same/different field of each linked issue to the selected field of the current 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

Use case

A typical use case for this workflow is to copy values of fields from issues linked to the current issue. Consider a use case where you want to copy Fix Version/s field from the Epic to a Story, while creating a Story. To configure this:

  1. Add the Copy field value from linked issues post-function to the Create transition of the Story workflow.

  2. Choose the has Epic link type.

  3. Select Fix Version/s in Source Field.

  4. Select Same as source field in the Destination field.

See here for more use cases