The As Atlassian offers a lot of APIs designed for Jira Service Management, you can use Web service node helps you to leverage such APIs and integrate Jira Service Management with Koji. It The Web service node sends a request to a web service , obtains, and parses the returned result. This page describes how to use this node.
| Table of Contents |
|---|
Jira Cloud Platform APIs
The REST APIs help developers integrate Jira Service Management with Koji. To learn more about JSM REST APIs functionality and view the references, visit the Atlassian Developer REST API portal.
Node prerequisites
Before using JSM APIs in your workflow, you must obtain the Session Auth Token, which is required for proper APIs performance. To do so:
...
Now you can start using JSM APIs in your workflows.
Web service node usage
Use the Web service node to send a request to a web service, obtain, and parse the returned result. Fill To configure the node, fill in the fields:
URI:specify the URL of Web Service that Kbot shall use.
Method: select the required method from the drop-down list:
POST,GET,PUT, orDELETE.Headers, Parameters, Body data: these fields are for the input data of the request. These parameters are sent to the service. Specify this data in accordance with the documentation of the API that you are using.
Patterns: save your request’s JSON results. You can save a result to the internal variable for the following usage in the Workflow. The patterns' data is stored as the
argument name - argument valuepairs.
Sample
Let’s create a workflow that returns a status for a given request. For such a workflow we are going to use the Get customer request by id or key method. It is used to return a given’s request status by ID or key. Our workflow will consists of multiple nodes described below.
...
3. In the workflow details view, click Edit workflow.
4. Create a the Call function node for obtaining the authorization details. In the Function name field, specify the wf.itsm.ticket.get_authorization_header function, which returns Session Auth Token. Save the result in a variable . For example, it can be (in this sample it is user_token).
...
5.
It returns the request status by ID or key.
We are creating a workflow that:
1. Obtaining the authorization using call function (above)
2. Asking user the request key
3. Getting ready the pass (Create the Ask node to ask a user their request key. Save the result in a variable (in this sample it is user_ticket).
...
6. Create the Save to short term memory node, name the property (in this sample it is get_request) and specify the method, as it is described in the Atlassian reference documentation).
...
4. Everything is ready for 7. Create the Web service node
5. Path is in URI field
6. In headers / auth we add auth that we got after call function
7. to get ticket status in patterns fields we are adding an variable for storing ticket status. the . Specify the URI, the API method type (as it is defined in the Atlassian documentation), headers (the Authorization comes from the first Call function node; Accept = application/json), and the pattern.
To get and utilize the ticket status later on in our workflow, in the Patterns section add a variable for storing the status. The value of this variable corresponds to the path in the response json object JSON object. For instance, the status in this case is $.currentStatus.status
testing
#workflow workflowname.
...
8. Click Save. Now you can test your workflow.
9. Open the chat and type the #workflow <workflow_name> chat command. In out sample, it is #workflow APItest.
10. Enter the key of your ticket and see its status. To check that everything is correct, you can open the ticket separately and make sure the result is accurate.
Debug
To view the debug information, type the #debug on command in a chat. It turns on the debug mode, so you can view processing and messaging details right in the chat.