---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Onboard Jira using Service Catalog

# Onboard Jira to DevOps Change Velocity --- Service Catalog {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read  
Create, connect, discover, and configure your Jira Server or Jira Cloud instance using the ServiceNow
Service Catalog.

## Before you begin

Role required: sn_devops.admin or sn_devops.tool_owner

## Procedure

1. Navigate to AllService CatalogCatalog DefinitionsMaintain Items and search for DevOps.  
   Note:  
   You can also access the service catalog from the Employee Center or Service portal.
2. From the DevOps catalog items, select and activate DevOps App Onboarding and DevOps Tool Onboarding.
3. After activating, select DevOps Tool Onboarding and select Try it.
4. In the DevOps Tool Onboarding form, enter the tool details:  
   {#sc-jira__table_bsr_hkv_kbc__entry__1}{#sc-jira__table_bsr_hkv_kbc__entry__3}

   | Jira Server | 1. In the Tool name field, enter a name for the tool. 2. In the Tool integration field, search for and select Jira. 3. Enter your Jira server instance URL. 4. From the Credential type list, select the authentication type you want to use to connect with your Jira server. * Basic Auth 1. Enter your Jira server username. Note: The Jira user that you use here must have the Jira Administrators permissions. 2. Enter the password or access token to access this instance. {#sc-jira__ol_ibm_jkv_kbc} * API Key Enter the API token to access the instance. {#sc-jira__ul_hbm_jkv_kbc} 5. If you want to configure webhooks for all the projects discovered in your Jira instance, then select the option Do you wish to configure webhook for the tool? 6. Select  Use MidServer for an on-premises tool that is attached to a  MID Server. Application is automatically set to  DevOps and capability is set to REST. {#sc-jira__ol_gbm_jkv_kbc} |
   | Jira Cloud | 1. In the Tool name field, enter a name for the tool. 2. In the Tool integration field, search for and select Jira Cloud. 3. in the Tool URL field, enter your Jira Cloud instance URL. 4. In the Credential type field, select Basic Auth or OAuth 2.0 with 3LO. Basic Auth 1. Enter your Jira Cloud username. Note: The Jira user that you use here must have the Jira Administrators permissions. 2. Enter the password or access token to access this instance. {#sc-jira__ol_kts_jgz_5cc} OAuth 2.0 with 3LO Select the OAuth credential record. For more information, see [Connect a Jira tool using OAuth 2.0 with 3LO](https://servicenow-prod.fluidtopics.net/yaHsfPSSbSCPPipSBU8x~w "Authenticate a Jira tool connection using OAuth 2.0 with three-legged OAuth (3LO) to enable secure, delegated access to your Jira account."). 5. If you want to configure webhooks for all the projects discovered in your Jira instance, then select the option Do you wish to configure webhook for the tool? Note: If you have connected your Jira tool using OAuth 2.0 based authentication, the webhooks are created for the OAuth 2.0 integration app in Jira when you configure automatically, whereas if you have connected using basic authentication, the webhooks are created for all your projects in Jira. 6. Select  Use MidServer for an on-premises tool that is attached to a  MID Server. Application is automatically set to  DevOps and capability is set to REST. {#sc-jira__ol_ubz_jkv_kbc} |
   |-|-|
   [ ]

   {#sc-jira__table_bsr_hkv_kbc}

   For a list of all the permissions required on the credentials for connecting to Jira, see Jira permissions in [Permissions required for DevOps tools](https://servicenow-prod.fluidtopics.net/rkQZOOxQSNdDZ7d5eHch0A "Permissions required in your third-party tool to connect to DevOps Change Velocity.").
5. Select Order Now.  
   A request is created. When the request is approved, the tool is created, connected, configured, and discovered.
6. From the DevOps catalog items, select DevOps App Onboarding and select Try it.
7. In the DevOps App Onboarding form, enter the details:  

   |-|-|
   | Are you creating a new app or adding to an existing one? | Select from the options whether to create a new app or use an existing app. |
   | App | Enter the name for the app that you're creating or using. |
   | Onboarding pipelines | Leave empty. |
   | Onboarding repositories | Leave empty. |
   | Onboarding plans | Enter the connected Jira tool name. |
   | Plans | Select the plans for which you want to import historical data. |
   | Import from and Import to | Select the dates for which you want to import the data. By default, the last 30 days are selected. You can choose to import data for a maximum of 90 days. |
   [ ]

   {#sc-jira__table_vb5_s3p_gwb}
8. Select Order Now.  
   A request is created. When the request is approved, the plan objects are associated to the app record, which enables real-time tracking. Historical data is also imported for the selected plans. The Track field is automatically enabled for imported plans.

*[\>]: and then