Date: Fri, 29 Mar 2024 10:02:40 +0000 (UTC) Message-ID: <1772412054.19.1711706560603@56ae898d6e33> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_18_260821293.1711706560602" ------=_Part_18_260821293.1711706560602 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This post-function is obsolete. While you may continue using this p= ost function, which will not be removed from JMWE, we recommend you use the= more powerful Set issue fields inste= ad for new automations.
To add 'Set field value of linked issues' post-function to a tra= nsition :
Click Edit for the workflow that has the tran= sition you wish to add the post-function on.
In the Workflow Designer, select the transition.
Click on Post Functions
in the properties panel.<=
/p>
Click on Add
post function
.
Select Set field value of linked issues
from the =
list of post-functions.
Click on Add
to add the post-function on the tran=
sition.
Select the field from the Field
drop-down.
Select the link type from the Issue Link Type
drop-down.
Input a value in the Value
field. To input the issue or lin=
ked issue or transition or current user information in the Value field see, H=
ow to insert information using Nunjucks annotations.
Click on Add
to add the post-function to the transition.
After adding, move the post-function to the appropriate position accordi=
ng to Placing post-function=
s in a transition document.
Known limitations of common to all post-functions:<=
/em>
Related links
When you add this post-function to a transition and trigger the transiti= on, the add-on sets the specified value(s) on the selected field of all iss= ues linked to the current issue through the selected link type. The va= lue 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 fiel=
ds), the string representation of a number, date or boolean value, or the s=
tring 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 use=
r 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 o=
bject or array of objects. It will take the Value
&nb=
sp;in the value template and parse it like a JSON string into a JavaScript =
object. This will be passed back to Jira as the value of the field. To=
learn about the JSON value expected by the post-functio=
n, see Expected value for each=
field type.
Copy only if not set: Sets the value of the select= ed field on all linked issues only if the field is empty on the linked issu= es.
Create missing value(s): Allows creating any missing Co= mponent/s or Version/s while setting or copying a field that expects Versio= ns or Components. Note this is applicable for version and component fields.=
Ignore empty value: Will not set (clear) the selected f=
ield of linked issue(s), if Value
is empty or null.<=
/p>
Add value(s) to the linked issue: Appends the specified= value(s) to the selected field of all the linked issues. This is applicabl= e only to multi-valued fields.
Send notifications: Jira sends notifications for the ch=
ange in the selected field value on the linked issue(s). You can contr=
ol the default value of the "Send notifications"
opt=
ion in the Configuration page under JMWE adminis=
tration. Click here for more =
information.
To execute this post-function based on th= e result of a Nunjucks template see Conditi= onal execution.
Run as current user: The current user will be the autho= r 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 d= iscouraged
If you select any option other than "Run as add-on user", so that the ch= ange appears to be done by the current user or a specific user, the followi= ng must be true:
The destination field must be present on the Edit scr= een applicable to the issue being modified
The selected user must have the Edit issues p= ermission on the issue being modified
Post functions are provided with an option to delay their execution= . You need to select the number of seconds to wait until the post-function is run, a default of 1 sec to a&n= bsp;maximum of 20 seconds.
Workflows that depend on post functions being executed in a specifi= c order fail due to the asynchronous nature of the Connect pos= t-functions in Jira Cloud. One of the workarounds is to delay the exec= ution 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-task= s 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-t= asks are created before they are transitioned. See the use case belo= w.
It is recommended to use the Sequence= of post-functions post-function or Shared Action post-function post-function to run a list of post-functi= ons in a sequence instead of applying a delay.
On the creation of a Bug, assign it to a memb= er of the QA team and then add the Assignee to the Watchers.
On the approval of a Story, create subta= sks for Development and QA, and transition them to In Progress st= atus.
Note that you can use this function to set the value of a field of the:<= /p>
parent issue of a sub-task by using the is Subtask of
=
link type and vice versa using the is Parent of
link=
type
Epic of an issue by using the belongs to Epic
link typ=
e and vice-versa using the is Epic of
link type
Parent of the portfolio hierarchy by using the belongs to Initiati=
ve
link type and vice-versa using the is Initiative of
=
link type