---
sourceDocument: Brazil Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Set up the Jira Service Management spoke

# Set up the Jira Service Management spoke {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Integrate the ServiceNow instance and Jira Service Management by using OAuth 2.0 to authenticate ServiceNow requests.

## Before you begin

* Request an Integration Hub subscription.
* Activate the Jira Service Management spoke.
* Role required: admin.
{#setup-jira-serv-mgmt__ul_agy_qxd_rlb}

## About this task

Important:  
Starting with the Australia release, instructions for generating and using API tokens have been removed from our documentation to align with Atlassian's Acceptable Use Policy. See the Atlassian blog, [Building Secure and Scalable Integrations: Our Guidance for Third-Party Apps](https://www.atlassian.com/blog/developer/building-secure-and-scalable-integrations-our-guidance-for-third-party-apps) for more information.

## Obtain the value of Cloud ID {#ariaid-title2}

Obtain the value of Cloud ID of the cloud instance. This value is required during the configuration of the connection record in your ServiceNow instance.

### Before you begin

Role required: admin

### Procedure

1. Log in to [Atlassian Administration](https://admin.atlassian.com/) as an admin.
2. Click Select against the required organization.
3. From the Jira Software product, click Manage product access.  
   A new window is opened and the URL is in this format: <kbd class="ph userinput">https://admin.atlassian.com/s/&lt;Cloud-ID&gt;/apps</kbd>.
4. Copy the value of the Cloud ID for later use.

## Configure a connection for the Jira Service Management spoke {#ariaid-title3}

Add and configure a Jira Service Management connection to authenticate ServiceNow requests in a Jira Service Management spoke.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. Click the Integrations tab.
3. Under Connections, the Outbound connections are displayed by default.
4. Locate the Jira_SM connection alias and click View Details.  
   * To configure the default connection and credential alias record that is shipped along with the Jira Service Management spoke, click View Details.
   * To manage more than one Jira Service Management spoke connection records, you should create a new child alias record by clicking Add Connection. For more information about using multiple connections, see [Supporting multiple connections](https://www.servicenow.com/docs/D9pGgVwvfvFrzWX3lknyWg "Support several connections to a single integration provider. Select connections for flows, subflows, and actions directly from a flow.").

   {#jira-sm-basic-conf-temp__ul_p54_wrr_qwb}If you are configuring the spoke for the first time, click Configure. Otherwise, click Edit.
5. On the Connection form, fill in the fields.  
   {#jira-sm-basic-conf-temp__table_tfv_3d5_h5b__entry__2}

   | Field | Description |
   |-|-|
   | Connection Name | Name to uniquely identify the connection. For example, <kbd class="ph userinput">Jira Spoke OAuth basic conn</kbd>. |
   | Connection URL | URL of your Jira instance in this format: <kbd class="ph userinput">https://api.atlassian.com/ex/jira/{cloud-id}/</kbd>. Replace <kbd class="ph userinput">{cloud-id}</kbd> with value of the Cloud ID you had obtained previously. |
   | Scopes | By default, these scopes are provided <kbd class="ph userinput">read:jira-user, read:servicedesk-request, write:servicedesk-request, manage:servicedesk-customer, read:jira-work, read:me, read:account, offline_access</kbd>. You can modify the scopes as per your requirement. Note: After the scopes are modified and saved, whenever you edit the connection record, the scopes are reset to the default scopes. |
   [ ]

   {#jira-sm-basic-conf-temp__table_tfv_3d5_h5b}

6. Click Save and Get OAuth Token.
{#jira-sm-basic-conf-temp__steps_kk1_4bz_t3c}

*[\>]: and then