This post-function is deprecated. We recommend using the more flexible Comment issue post-function instead. However, existing Comment Linked Issues post-functions will continue to work.
To add 'Comment 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.
Comment linked issuesfrom the list of post-functions.
Addto add the post-function on the transition.
Select the link from the
Issue Link Typedrop-down.
Input a comment in the
To input issue or linked issue or transition or current user information in the
Commentfield see, How to insert information using Nunjucks annotations.
Select the options provided to add the required parameters.
After adding, move the post-function to the appropriate position according to Placing post-functions 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:
Troubleshooting this post-function configuration: In case the post-function does not work as expected these are the things to look out for
When you add this post-function to a transition and trigger the transition, the add-on picks the value entered in the
Comment field and adds it as a comment on all the issues linked to the current issue through the selected link type. The
Comment to be created can be any simple text, e.g.
This is a comment. You can also use Nunjucks annotations to insert issue, linked issue, transition and current user information into the comment text, using the 'issue', 'linkedIssue', 'transition' and 'currentUser' variables, respectively. To find out more about these variables, see How to insert information using Nunjucks annotations.
Restrict to Group: Restricts the visibility of the comment to a specified group. When you select a valid group name in the
Restrict to Groupfield, the comment will be visible only to the members of the specified group. For no restriction, leave the field blank.
Restrict to Project Role: Restricts the visibility of the comment to a selected project role. When you select a project role from the
Restrict to Project Roledrop-down, the comment will be visible only to the members of the selected project role. For no restriction, leave the field blank.
Restrict to Internal (Jira Service Desk only): Restricts the visibility of the comment to the Service Desk Agents and Collaborators only.
Run as current user: The current user will be the author of the comment created on the linked issues by the post-function.
Run as add-on user: The add-on user will be the author 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 the result of a Nunjucks template see Conditional execution.
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 comment the:
parent issue of a sub-task by using the built-in
is Subtask oflink type and vice versa using the
is Parent oflink type
Epic of an issue by using the built-in
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