Date: Fri, 29 Mar 2024 15:04:04 +0000 (UTC) Message-ID: <1614226012.9.1711724644020@fa2808ff97f9> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8_2145546853.1711724644018" ------=_Part_8_2145546853.1711724644018 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 Comment Issue(s) inste= ad for new automations.
To add 'Comment linked issues' post-function to a transition :&n= bsp;
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.
Click on Add
post function
.
Select Comment linked issues
from the list of pos=
t-functions.
Click on Add
to add the post-function on the tran=
sition.
Select the link from the Issue Link Type
drop-down.
Input a comment in the Comment
field.
To input issue or linked issue or transition or current user information in=
the Comment
field see, How to insert information using Nunjucks annotations<=
/a>.
Select the options provided to add the required parameters.
After adding, move the post-function to the appropriate position accordi= ng to Placing post-function= s in a transition document.
Here are a few Use cases for this post-function.
Known issues common to all post-functions:
Known issues specific to this post-function:= p>
Troubleshooting this post-function configuration: <= /em>In case the post-function does not work as expected these are the thing= s to look out for
When you add this post-function to a transition and trigger the transiti=
on, the add-on picks the value entered in the Comment
field and adds it as a comment on all the issues linked to the curre=
nt issue through the selected link type. The Comment
=
to be created can be any simple text, e.g. This is a comme=
nt.
You can also use N=
unjucks annotations to insert issue, linked issue, t=
ransition and current user information into the comment text, using the 'is=
sue', 'linkedIssue', 'transition' and 'currentUser' variables, respectively=
. To find out more about these variables, see How to insert information using Nunjucks ann=
otations.
Restrict to Group: Restricts the visibility of the comm=
ent to a specified group. When you select a valid group name in the
Restrict to Project Role: Restricts the visibility of t=
he comment to a selected project role. When you select a project role from =
the Restrict to Project Role
drop-down, the comment =
will be visible only to the members of the selected project role. For no re=
striction, leave the field blank.
Restrict to Internal (Jira Service Desk only): Restrict= s the visibility of the comment to the Service Desk Agents and Collabo= rators only.
Run as current user: The current user will be the autho= r of the comment created on the linked issues by the post-function.&nb= sp;
Run as add-on user: The add-on user will be the au= thor of the comment created on the linked issues by the post-function.=
Run as this user: Any user selected in this field will = be the author of the comment created on the linked issues by the = post-function.
To execute this post-function based on th= e result of a Nunjucks template see Conditi= onal execution.
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 comment the:
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<=
/p>
Epic of an issue by using the built-in belongs to Epic
link=
type 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