Let's add the same comment to the linked issue.

This tutorial describes how a group's members can be added as watchers on a transition, such as in this example Create Issue.

Assumption

In our TESTB project, we got two issues linked together with inward "is caused by". When we comment on the issue it shall add a comment to the linked issue as well.

Steps

1. Create a new Action by clicking CREATE button
2. Enter a name: Get Linked Issue and click CREATE
3. Select Method: GET and URL: <your_base_url>/rest/api/2/issue/{{issue.key}}?fields=issuelinks
   From the Atlassian REST API we can read that to fetch issue links by getting the issue JSON and further filter it by fields=issuelinks. call GET /rest/api/2/issue/{{issue.key}}?fields=issuelinks
   
4. Select Authentication method: Basic Auth, specify a user with comment and browse permissions
5. Add request headers, key: Content-Type with value application/json
6. Click Triggers tab
7. Select ISSUE COMMENTED event
8. On JQL Condition. When to execute the event(s) write project = TESTB AND issueLinkType = "is caused by"  to limit the trigger to the TESTB project and only the direction of "is caused by".
9. Click SAVE
10. (Optional) Click Test button (no issue key is needed) to and click Send, Then go View Execution Log.

Each result will have a response like the one below:

{
  "self": "https://support.rixter.se/rest/api/2/project/11100/role/10100",
  "name": "Developers",
  "id": 10100,
  "actors": [
    {
      "id": 12204,
      "displayName": "Mr Bot",
      "type": "atlassian-user-role-actor",
      "name": "mr.bot@rixter.se",
      "avatarUrl": "https://support.rixter.se/secure/useravatar?size=xsmall&ownerId=mr.bot%40rixter.se&avatarId=10601"
    },
    {
      "id": 12205,
      "displayName": "Rickard Atthem",
      "type": "atlassian-user-role-actor",
      "name": "rick",
      "avatarUrl": "https://support.rixter.se/secure/useravatar?size=xsmall&ownerId=rick&avatarId=10600"
    }
  ]
}

Next steps are to add the users as watchers

1. Create a new Action by clicking CREATE button

2. Enter a name: Comment linked issue and  note on the Select parent action choose to Get Linked Issue which we created in part 1 and click CREATE
   This will create a chained action that will be triggered directly after the response from the parent action is received. The response will be used as input variables this call using JSON Path expressions.

3. A new section called Variables is now displayed. On this section enter the Variable name: inwardIssue and the JSON Path: $.fields.issueLinks[0].inwardIssue.key
   The JSON path will return a variable with the value of the linked issue key.
4. Select Method: POST and URL: <your_base_url>/rest/api/2/issue/{{issue.key}}/watchers
    note that we use double curly brackets {{issue.key}} to operate on the issue. Within the brackets, we can access any issue property.
   From the Atlassian REST API we can read that to add watchers we need to call POST /rest/api/2/issue/{issueIdOrKey}/watchers
5. Select Authentication method: Basic Auth, specify an admin user that can read groups in JIRA.
6. Add request headers, key: Content-Type with value application/json

7. In Body section add the following payload body

   {{#watchers}}
   "{{.}}"
   {{/watchers}}
   
   {{^watchers}}
   "{{.}}"
   {{/watchers}}

   Since we get an array of usernames as a result from the JSON Path$.actors[*].name value [rick,mr.bot@rixter.s] and the API endpoint requires a comma-separated list of strings we need to render that in the body using the Mustache template. Accessing the watchers variable with double brackets and then using the iteration method to walk through the list. Therefore the # and / syntax. The ^ and  / removes the last comma.

8. Click SAVE button
9. (Optional) Click Test button (no issue key is needed) to and click Send, Then go View Execution Log