Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Let's add the same comment to the linked 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

Part 1 - Get the linked issue

  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:

{
	"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",
	"id": "12837",
	"self": "https://support.rixter.se/rest/api/2/issue/12837",
	"key": "TESTB-7",
	"fields": {
		"issuelinks": [
			{
				"id": "11102",
				"self": "https://support.rixter.se/rest/api/2/issueLink/11102",
				"type": {
					"id": "10300",
					"name": "Problem/Incident",
					"inward": "is caused by",
					"outward": "causes",
					"self": "https://support.rixter.se/rest/api/2/issueLinkType/10300"
				},
				"inwardIssue": {
					"id": "12839",
					"key": "TESTB-8",
					"self": "https://support.rixter.se/rest/api/2/issue/12839",
					"fields": {
						"summary": "Linked issue test",
						"status": {
							"self": "https://support.rixter.se/rest/api/2/status/10003",
							"description": "",
							"iconUrl": "https://support.rixter.se/",
							"name": "To Do",
							"id": "10003",
							"statusCategory": {
								"self": "https://support.rixter.se/rest/api/2/statuscategory/2",
								"id": 2,
								"key": "new",
								"colorName": "blue-gray",
								"name": "To Do"
							}
						},
						"priority": {
							"self": "https://support.rixter.se/rest/api/2/priority/4",
							"iconUrl": "https://support.rixter.se/images/icons/priorities/low.svg",
							"name": "Low",
							"id": "4"
						},
						"issuetype": {
							"self": "https://support.rixter.se/rest/api/2/issuetype/10002",
							"id": "10002",
							"description": "A task that needs to be done.",
							"iconUrl": "https://support.rixter.se/secure/viewavatar?size=xsmall&avatarId=10318&avatarType=issuetype",
							"name": "Task",
							"subtask": false,
							"avatarId": 10318
						}
					}
				}
			}
		]
	}
}


Part 2 - Get the last comment (this step will in the future be replaced by a smart function)

  1. Create a new Action by clicking CREATE button
  2. Enter a name: Get Last Comment and click CREATE
  3. Select Method: GET and URL: <your_base_url>/rest/api/2/issue/{{issue.key}}/comment
    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/{issueIdOrKey}/comment
  4. A new section called Variables is now displayed. On this section enter the Variable name: lastComment and the JSON Path$.comments[(@.length-1)].body
    The JSON path will return a variable with the value of the last comment
  5. Select Authentication method: Basic Auth, specify a user with browse permissions
  6. Add request headers, key: Content-Type with value application/json
  7. Click SAVE
  8. (Optional) Click Test button (no issue key is needed) to and click Send, Then go View Execution Log.

Part 3 - Add the last comment to linked issue

  1. Create a new Action by clicking CREATE button
  2. Enter a name: Comment linked issue and (warning) note on the Select parent action choose to Get Last Comment 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/{{inwardIssue}}/comment
    note that we now use the inwardIssue in the URL that we post to.
    From the Atlassian REST API we can read to comment on an issue we need to call POST /rest/api/2/issue/{{issue.key}}/comment
  5. Select Authentication method: Basic Auth, specify a user that has comment permission in the project
  6. Add request headers, key: Content-Type with value application/json
  7. On the Body section add the following

    {
        "body":"{{lastComment}}"
    }
  8. Click SAVE
  9. (Optional) Click Test button, Issue Key needs to be provided and click Send, Then go View Execution Log.


  • No labels