Integration with Jira using Jira Spoke

Pre Requisites:

IntegrationHub Subscription

What the Jira Spoke does?

• Issue Management
• Project Management
• SDLC Management
• User Management
• Group Management
• Metadata retrieval
• Sprint Management
• Utility Actions
• WebHook Management

Retrieves Jira data to use in a flow.

Jira Spoke provides a concept of Bi-directional webhooks that notifies about the events occurred in Jira for example. updation of an existing issue, when an issue is assigned to a particular user etc.

Bi-directional WebHook:

This has 2 modules:

• Jira WebHook Registries(these are used to assign a token and API path. We need to generate a call back URL from here and provide it in Jira)
• Jira WebHook Routing Policies(these triggers the subflows based on the conditions specified)

Note:

• ServiceNow provides a default routing policy which needs to be modified according to the requirement.
• Jira Spoke provides a default subflow to process the WebHook events

Integration Steps:

Step -1: Setup Credential in ServiceNow

• In ServiceNow Instance, Navigate to Integration Hub > Credentials
• Click on “Jira” the entry created by the spoke. Provide the username and for the password, go back to Jira and in Account Setting> Security> Create and Manage API token>Create API token
• Give a label and click on “Create” and “Copy” the token.
• Switch back to ServiceNow and paste this token in “Password” field and update this record.

Credentials has been setup

Step-2: Setup Connection in ServiceNow

• In ServiceNow Instance, Navigate to Integration Hub > Connections
• Click on “New” and “HTTP(s) connection”
• Provide a random Name in the “Name” field. Select the credential that we have selected in step-1 in “credential” column.
• Connection Alias is referencing the Jira spoke. So select the Jira spoke in this column.
• Connection URL is the hostname of the Jira application.
• Click on “Submit”

Step-3: Check Connection and Credential Aliases

• In ServiceNow Instance, Navigate to Integration Hub > Connection & Credential Aliases.
• Click on “Jira” and check that credentials and connections are interconnected with each other.

Step-4: Create a Flow Designer

• In ServiceNow Instance, Navigate to Flow Designer > Designer
• Create a new Flow-Give a name and Submit
• In the trigger, create a trigger condition like when this Jira integration needs to be triggered.
• In the next step – Actions, Create a new action- Search for “issue or Jira” and click on “Create an Issue”
• Provide Project Key, Issue Type and Summary, Click on “Done”
• For correlating these two, Jira provides back some parameters. Here we can use Issue ID and map that to the record(incident or task etc..)
• For mapping the Jira Parameters to ServiceNow record, as the next step in Flow Designer, create an other action “Update Record” and map the respective fields or add the parameters to the worknotes etc.

So Jira Setup is now done 

Test this

Step-5: Make this Bidirectional

• To make this Bi-Directional, we will create a webhook in ServiceNow.
• For creating a webhook, navigate to Jira Webhooks> Jira Webhook Registries and click on “New”
• Provide a random name in “name “Column and Select the built-in token i.e. Jira Token in the “Token” column
• So next thing is to get the callback URL for Jira to talk to ServiceNow.
• To do this, go back to webhook registry that we have created and click on “callback URL”. Copy the URL from the information box.
• Now go back to Jira and open General Configuration and open Webhooks.
• Create a new Webhook in Jira Application (Specify random name and paste the URL copied from SNOW into the URL field). Also please check when the issue is update checkbox. And click on “Create”
• Now go back to ServiceNow instance and create a subflow in flow designer.
• There is a default subflow “Process Jira WebHook”. Make a copy of this subflow
• In the subflow, create an action “Lookup up Record” and find the incident where correlation id is issue ID
• Create another action for updating the record. For example, update the worknotes with the resolution or description etc. sent from Jira.
• Now we are going to tell webhook which subflow to be called

Step-6: Create Jira Webhook Routing policies

• There is a OOB decision. Update this with the sub flow that we have created.

Please do mark helpful and bookmark if possible. Thank you for reading.