Rule response determine what the incoming rule will respond to the caller.
There are three options available
Option 1: No response, 200 OK
Option 2: Custom Response
Any text that you want to pass back to the caller.
Option 3: Action response
This will wait until the triggered action has completed and return back the full payload and response.
Leave the Filter response using mustache text box empty to echo the response.
{
"actionId": 1,
"actionName": "created iss",
"httpStatusCode": 201,
"responseData": {
"id": "10300",
"key": "DFGHJ-51",
"self": "http://localhost:2990/jira/rest/api/2/issue/10300"
},
"requestData": {
"headers": {
"Authorization": "*******",
"Accept": "application/json",
"Content-Type": "application/json"
},
"body": "{\n \"fields\": {\n \"project\": {\n \"id\": \"10000\"\n },\n \"summary\": \"something's wrong\",\n \"issuetype\": {\n \"id\": \"10001\"\n },\n \"description\": \"description\"\n \n }\n}",
"url": "http://localhost:2990/jira/rest/api/2/issue",
"method": "POST",
"formVars": {}
}
}
Example a create issue action response
Filtering
The response could be to much info for the caller to receive, in that case you can filter the response with the custom response text box.
{
"data":{{{responseData.asJson}}},
"key":"{{{responseData.key}}}"
}
This will result in a json like the example below.
