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
- Create a new Action by clicking
buttonStatus colour Blue title Create - Enter a name: Get Linked Issue and click
Status colour Blue title Create - Select Method:
and URL: <your_base_url>/rest/api/2/issue/{{issue.key}}?fields=issuelinksStatus colour Yellow title GET
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 - Select Authentication method: Basic Auth, specify a user with comment and browse permissions
- Add request headers, key: Content-Type with value application/json
- Click Triggers tab
- Select
eventStatus colour Green title Issue Commented - 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".
- Click
Status colour Blue title SAVE - (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:
Code Block | ||
---|---|---|
| ||
{
"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
- Create a new Action by clicking
buttonStatus colour Blue title Create 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
Status colour Blue title 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.- 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. - Select Method:
and URL: <your_base_url>/rest/api/2/issue/{{issue.key}}/watchersStatus colour Yellow title POST
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 - Select Authentication method: Basic Auth, specify an admin user that can read groups in JIRA.
- Add request headers, key: Content-Type with value application/json
In Body section add the following payload body
Code Block language java {{#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.
- Click
buttonStatus colour Blue title SAVE - (Optional) Click Test button (no issue key is needed) to and click Send, Then go View Execution Log