---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Configure Atlassian Jira Cloud for external content indexing

# Configure Atlassian Jira Cloud for external content indexing {#ariaid-title1}

* Release version: Xanadu
* 
* Updated June 25, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Register an OAuth 2.0 integration in the Atlassian Developer console and create an API key in Atlassian Administration to allow the Atlassian
Jira Cloud external content connector to crawl projects and security principals in your Atlassian
Jira Cloud source system.

## Before you begin

You need the following credentials and permissions for your organization's Atlassian management applications:{#cfg-src-sys-settings-jira-ext-cont-connector__table_wr3_s1q_xdc__entry__2}

| Atlassian portal | Required credentials and permissions |
|-|-|
| Atlassian Developer console (<https://developer.atlassian.com/console/myapps/>) | * Login credentials * Permission to view settings for registered applications * Permission to register a new application * Permission to set granular Jira API scopes for an application * Permission to set the OAuth 2.0 callback URL for an application {#cfg-src-sys-settings-jira-ext-cont-connector__ul_bg4_51q_xdc} |
| Atlassian Administration (<https://admin.atlassian.com/>) | * Login credentials * Permission to create a new admin API key {#cfg-src-sys-settings-jira-ext-cont-connector__ul_r45_51q_xdc} |
[ ]

{#cfg-src-sys-settings-jira-ext-cont-connector__table_wr3_s1q_xdc}

Role required: admin

## About this task

The Atlassian Jira Cloud external content connector retrieves content from your Atlassian Jira Cloud source system using the Jira API.

To allow the connector to access your Atlassian Jira Cloud source system via the Jira API, you must configure an OAuth 2.0 integration in the Atlassian Developer console and an API key in Atlassian Administration. Your search administrator can use settings copied from the OAuth 2.0 integration and the API key to configure the Atlassian Jira Cloud external content connector for proper connection to your Atlassian Jira Cloud source system.

## Procedure

1. Find the instance ID for your Atlassian Jira Cloud tenant.
   1. Navigate to https://\<tenant-name\>.atlassian.net/_edge/tenant_info, replacing <kbd class="ph userinput">&lt;tenant-name&gt;</kbd> with the name of your Atlassian Jira Cloud tenant.  
      The web endpoint displays a JSON response showing the cloud ID (instance ID) for your tenant.

      ![Cloud ID for Atlassian Jira Cloud shown in JSON format.]()
   2. Record the value of the cloudId JSON parameter in a secure location.  
      Important:  
      Your AI Search administrators need this instance ID value when configuring the Atlassian Jira Cloud external content connector. {#cfg-src-sys-settings-jira-ext-cont-connector__record-cloud-id}
   {#cfg-src-sys-settings-jira-ext-cont-connector__record-cloud-id} {#cfg-src-sys-settings-jira-ext-cont-connector__substeps_gjd_kh4_s2c}
2. In the Atlassian Developer console, register a new OAuth 2.0 integration for the Atlassian Jira Cloud external content connector.
   1. Login to the Atlassian Developer console at <https://developer.atlassian.com/console/myapps/>.
   2. In the My apps section, select CreateOAuth 2.0 integration.  
   3. Enter a name for your OAuth 2.0 integration, select the option to agree to Atlassian's developer terms, and select Create.  

      As an example, you might enter <kbd class="ph userinput">Jira Cloud external content connector</kbd> as the name for your OAuth 2.0 integration.
   4. Navigate to the OAuth 2.0 integration's Permissions page, then select Add in the Jira API row.  
   5. In the Jira API row, select Configure.  
   6. On the Granular scopes tab, select Edit Scopes and then select the options for each of the following scopes:  
      * read:application-role:jira
      * read:attachment:jira
      * read:audit-log:jira
      * read:avatar:jira
      * read:comment.property:jira
      * read:comment:jira
      * read:field-configuration:jira
      * read:field:jira
      * read:group:jira
      * read:issue-details:jira
      * read:issue-meta:jira
      * read:issue-security-level:jira
      * read:issue-security-scheme:jira
      * read:issue-type-hierarchy:jira
      * read:issue-type:jira
      * read:issue.changelog:jira
      * read:issue.vote:jira
      * read:issue:jira
      * read:permission-scheme:jira
      * read:permission:jira
      * read:project-category:jira
      * read:project-role:jira
      * read:project-type:jira
      * read:project-version:jira
      * read:project.component:jira
      * read:project.feature:jira
      * read:project.property:jira
      * read:project:jira
      * read:status:jira
      * read:user.property:jira
      * read:user:jira

      {#cfg-src-sys-settings-jira-ext-cont-connector__ul_nbj_zlp_xdc}
   7. Select Save.  
   8. Navigate to the OAuth 2.0 integration's Authorization page, then select Add in the row for the OAuth 2.0 (3LO) authorization type.  
   9. Enter https://\<instance-name\>.service-now.com/oauth_redirect.do as the callback URL, replacing <kbd class="ph userinput">&lt;instance-name&gt;</kbd> with your ServiceNow AI Platform® instance name, then select Save changes.  
   10. Navigate to the OAuth 2.0 integration's Settings page and record the Client ID and Secret values in a secure location.  
       Important:  
       Your AI Search administrators need these Client ID and Secret values when configuring the Atlassian Jira Cloud external content connector. {#cfg-src-sys-settings-jira-ext-cont-connector__record-client-id-and-secret-step}
   {#cfg-src-sys-settings-jira-ext-cont-connector__record-client-id-and-secret-step} {#cfg-src-sys-settings-jira-ext-cont-connector__substeps_sjm_ywp_xdc}
3. In Atlassian Administration, create a new admin API key.
   1. Login to Atlassian Administration at <https://admin.atlassian.com/>.
   2. Select Settings in the tab list.  
      ![Atlassian Administration console Settings tab.]()
   3. Select API keys, then select Create API key.  
   4. On the Before you begin page, select API key without scopes, then select Next.  
   5. Enter a name and an expiration date for your new API key.  

      As an example, you might enter <kbd class="ph userinput">Jira Cloud external content connector</kbd> as the name for your API key and set its expiration date to be one year in the future.
   6. Select Create.
   7. Record the value of the API key in a secure location.  
      Important:  
      Your AI Search administrators need the API key's value when configuring the Atlassian Jira Cloud external content connector. {#cfg-src-sys-settings-jira-ext-cont-connector__record-api-key}
   {#cfg-src-sys-settings-jira-ext-cont-connector__record-api-key}
   8. Select Done.
   {#cfg-src-sys-settings-jira-ext-cont-connector__substeps_fws_pxp_xdc}
4. Configure a technical user in your Atlassian Jira Cloud tenant to allow access by the Atlassian Jira Cloud external content connector.  
   For details on this procedure, see [Configure a connector user in Atlassian Jira Cloud](https://servicenow-prod.fluidtopics.net/2kreay8bY4~gwyyNFSpG0w "Create a user and group in your Atlassian Jira Cloud tenant with access and permissions required by the Atlassian Jira Cloud external content connector. The connector runs as this user when accessing data from your tenant."). {#cfg-src-sys-settings-jira-ext-cont-connector__configure-technical-user-step}
{#cfg-src-sys-settings-jira-ext-cont-connector__configure-technical-user-step}

## What to do next

Provide the following items to your AI Search administrator:

* The instance ID (cloud ID) value that you recorded in step [1.b](https://servicenow-prod.fluidtopics.net/xAbVIaQfBH8S_mSn~GTOGQ#cfg-src-sys-settings-jira-ext-cont-connector__record-cloud-id).
* The OAuth 2.0 integration's Client ID and Secret values that you recorded in step [2.j](https://servicenow-prod.fluidtopics.net/xAbVIaQfBH8S_mSn~GTOGQ#cfg-src-sys-settings-jira-ext-cont-connector__record-client-id-and-secret-step).
* The API key's value that you recorded in step [3.g](https://servicenow-prod.fluidtopics.net/xAbVIaQfBH8S_mSn~GTOGQ#cfg-src-sys-settings-jira-ext-cont-connector__record-api-key).
* The credentials for the Atlassian Jira Cloud user that you created in step [4](https://servicenow-prod.fluidtopics.net/xAbVIaQfBH8S_mSn~GTOGQ#cfg-src-sys-settings-jira-ext-cont-connector__configure-technical-user-step).
{#cfg-src-sys-settings-jira-ext-cont-connector__ul_wyj_3zp_xdc}

Your AI Search administrator needs these items to configure an Atlassian
Jira Cloud external content connector to retrieve projects and security principals from your Atlassian
Jira Cloud instance.

For details on creating and configuring an Atlassian
Jira Cloud external content connector, see [Create an Atlassian Jira Cloud external content connector](https://servicenow-prod.fluidtopics.net/UYCPzM~nebG6r1uY096kPw "Create an external content connector to retrieve searchable content and security principals from your Atlassian Jira Cloud source system.").
* **[Configure a connector user in Atlassian Jira Cloud](https://servicenow-prod.fluidtopics.net/2kreay8bY4~gwyyNFSpG0w)**   
  Create a user and group in your Atlassian Jira Cloud tenant with access and permissions required by the Atlassian Jira Cloud external content connector. The connector runs as this user when accessing data from your tenant.

*[\>]: and then