Our new Appfire Documentation Space is now live!

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

Set field value of linked issues

Owned by Radhika Vijji. (Unlicensed)
Last updated: Dec 04, 2019
3 min read

Documentation for JMWE 6.2.0 is available here.

A workflow post-function that sets the value(s) of a selected field of all issues linked to the current issue through a selected link type. The value can be either a constant, optionally including a Groovy template markup, or the result of the evaluation of a Groovy expression.

This post-function does not work with remote links (links to Jira issues residing on another Jira instance/server).

To add the 'Set field value of linked issues' post-function to a transition:

  1. Click Edit for the workflow that has the transition you wish to configure 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 Set field value of 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 link type from the Issue Link drop-down.
  9. Select the value type in the Value type drop-down.
  10. Input a value in the Value field based on the value type selected in step 9.
  11. Click on Add to add the post-function to the transition.

Related links :

For information on where the post-function needs to be placed on a transition, see Placing post-functions on a transition.

Refer to the Use cases for post-functions page for use cases for this post-function.

When you add this post-function to a transition and trigger it, the add-on sets the specified value(s) on the selected field of all issues linked to the current issue through a selected link type. The value can be either a:

  • Constant or Groovy Template: You can set the field to a constant value optionally using Groovy Template markup to insert dynamic content. For example: To set the Description of the issue, you can specify This bug has been raised by <%=issue.get("reporter").getName()%> with <%=issue.get("priority").getName()%> priority. Act accordingly. in the value box.
  • Groovy expression: You can set the field to the result of a Groovy expression. For example, to set the Assignee to the Reporter of the issue, you can specify issue.get("reporter") in the value box.

See the Expected Value tab of the Groovy help editor or refer to the documentation to know more about the expected value in the above cases.

"Relates to" link type

Beware of the default "relates to" link type, which can cause confusion. The problem stems from the fact that "relates to" is both the inward direction and the outward direction of the "Relates" link type. We recommend that you rename one of the directions to "is related to" to avoid confusion. This can be done on the Issue Linking Jira admin page.

Options

  • Set only if empty

Sets the value of the selected field on all linked issues only if the field is empty on the linked issues.

  • Ignore empty values

Will not set (clear) the selected field of linked issue(s), if Value is empty or null.

  • Add source value(s) to destination field

Appends the specified value(s) to the selected field of all the linked issues. This is applicable only to multi-valued fields.

  • Create missing value(s)

Allows automatically creating any missing value(s) while setting a field value of linked issue(s). 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.

Run as

  • Run as user

Any user specified in this field will be the author of the copy performed by the post-function. Leave it blank for the current user to be the author.

Conditional execution

To execute this post-function based on the result of a groovy expression see Conditional execution/validation using a Groovy expression.

Error Handling

By default, all errors (Java Exceptions) raised by this post-function, including those raised by custom Groovy scripts, will be logged in the JIRA log file but will not be reported to the user and will not prevent the transition from completing. 

However, when designing new workflows or troubleshooting them, it is more convenient to be notified immediately of any such error during the execution of the transition. On development and staging Jira instances, you can activate error reporting for all JMWE post-functions on the JMWE configuration page, and it is recommended to do so. But on production Jira instances, you might want to show errors only for the post-function(s) being worked on, in order to avoid disrupting other workflows. To make errors raised by the current post-function prevent the transition from completing and show the error in the browser, select Make transition fail when an error occurs in this post-function.