This post-function is deprecated. We recommend using the more flexible Set field value post-function instead. However, the existing Set field value of linked Issues post-functions will continue to work.
To add 'Set field value of linked issues' 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.
Post Functionsin the properties panel.
Set field value of linked issuesfrom the list of post-functions.
Addto add the post-function on the transition.
Select the field from the
Select the link type from the
Issue Link Typedrop-down.
Input a value in the
Valuefield. To input the issue or linked issue or transition or current user information in the
Valuefield see, How to insert information using Nunjucks annotations.
Addto 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.
Known limitations of common to all post-functions:
When you add this post-function to a transition and trigger the transition, the add-on sets the specified value(s) on the selected field of all issues linked to the current issue through the selected link type. The value can be provided either as text (with optional Nunjucks annotations) or as a JSON value.
In the case of text, it can be a simple string (for text typed fields), the string representation of a number, date or boolean value, or the string representation of a complex value, such as a Version name, a username, a Project key, etc. Multiple values can be separated by commas. You can also use Nunjucks annotations to insert issue, linked issue, transition and current user information into
Value, using the 'issue', 'linkedIssue', 'transition' and 'currentUser' variables, respectively.
In the case of a JSON value, which requires the option
Treat value as JSON(explained below), it can be a String, a Number, a Boolean or an Object. It can also be an array of such values.
To find out more about the type of value expected by this post-function for each field type, see Expected value for each field type.
Treat value as JSON: Sets the field value from a JSON object or array of objects. It will take the
Copy only if not set: Sets the value of the selected field on all linked issues only if the field is empty on the linked issues.
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 linked issue(s), if
Valueis empty or null.
Add value(s) to the linked issue: Appends the specified value(s) to the selected 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 the linked issue(s). You can control the default value of the
"Send notifications"option in the Configuration page under JMWE administration. Click here for more information.
To execute this post-function based on the result of a Nunjucks template see Conditional execution.
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
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.
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.
Note that you can use this function to set the value of a field of the:
parent issue of a sub-task by using the
is Subtask oflink type and vice versa using the
is Parent oflink type
Epic of an issue by using the
belongs to Epiclink type and vice-versa using the
is Epic oflink type
Parent of the portfolio hierarchy by using the
belongs to Initiativelink type and vice-versa using the
is Initiative oflink type