---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/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 Workspace

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

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 minutes to read

Connect to your Jira Server or Jira Cloud instance from the DevOps Change Workspace to discover available plans and register webhooks to track projects, stories, features, and epics.

## Before you begin

Complete the tasks specified in the [Getting started with DevOps Change Velocity](https://www.servicenow.com/docs/zYfXM71OMizgQDlC6XiIiA "Learn about the setup process for DevOps Change Velocity that is required before configuring integrations with your toolchain.") topic.

Role required: sn_devops.admin or sn_devops.tool_owner

## Procedure

1. Navigate to WorkspacesDevOps Change Workspace and use one of the following options to open the Playbook to onboard Jira.

   | Option | Steps |
   | Homepage | 1. Select Connect a tool. 2. On the  Connect to a tool  modal, select Jira from the Plan category. {#create-jira-tool-dev-ops__ol_e5j_4y1_fwb} |
   | Applications module | 1. Select Applications (![Applications icon.]()) from the primary navigation. 2. Select an existing application, or create one. To create an application, see [Create an application - Workspace](https://www.servicenow.com/docs/0Q3U7QvoyazFAJLrEFh1bg "Create applications using the DevOps Change Workspace and associate pipelines, plans, and repositories to it."). 3. From the  Recommended actions  pane, select the  Connect a tool  card. 4. On the  Connect to a tool  modal, select Jira from the Plan category. {#create-jira-tool-dev-ops__ol_u24_mz1_fwb} |
   | Tools module | 1. Select Tools (![Tools icon.]()) from the primary navigation. 2. From the Capability list, select Planning. 3. Select Connect a tool. 4. On the  Connect to a tool  modal, select Jira. {#create-jira-tool-dev-ops__ol_fjs_k1b_fwb} |
   |-|-|

   {#create-jira-tool-dev-ops__choicetable_m3t_ky1_fwb}  
   Important:  
   If you want to discover and track tool objects like plans while connecting to the tool, you must connect your tool from the Application module.
2. Connect to your Jira Server or Jira Cloud instance.  
   {#create-jira-tool-dev-ops__table_h2d_2lv_kbc__entry__1}{#create-jira-tool-dev-ops__table_h2d_2lv_kbc__entry__3}

   | Jira Server | 1. From the Platform list, select Jira Server. 2. In the Tool name field, enter a name for the tool. This name is used to identify your Jira instance from the list of tools connected to DevOps Change Velocity. {#create-jira-tool-dev-ops__ol_i23_flv_kbc} |
   | Jira Cloud | 1. From the Platform list, select Jira Cloud. 2. In the Tool name field, enter a name for the tool. This name is used to identify your Jira instance from the list of tools connected to DevOps Change Velocity. {#create-jira-tool-dev-ops__ol_nhw_flv_kbc} |
   |-|-|
   [ ]

   {#create-jira-tool-dev-ops__table_h2d_2lv_kbc}
3. Select Next.  
   The DevOps playbook page opens to help you complete the onboarding tasks.
4. Complete the connection to your Jira tool using the playbook.
   1. Enter the connection details.  
      {#create-jira-tool-dev-ops__table_zld_3lv_kbc__entry__1}{#create-jira-tool-dev-ops__table_zld_3lv_kbc__entry__3}

      | Jira Server | 1. Enter your Jira server instance URL. 2. 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. {#create-jira-tool-dev-ops__ol_sr3_jlv_kbc} * API Key Enter the API token to access the instance. {#create-jira-tool-dev-ops__ul_rr3_jlv_kbc} 3. If your Jira instance is attached to a MID Server, select the MID Server option and enter its details. For more information about MID server, see [MID Server selection](https://www.servicenow.com/docs/access?context=c_MIDServerSelector&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) {#create-jira-tool-dev-ops__ol_qr3_jlv_kbc} |
      | Jira Cloud | 1. Enter your Jira Cloud instance URL. Note: If you select the credential type as OAuth 2.0 with 3LO in the next step, you must enter your Jira instance URL in the following format: https://api.atlassian.com/ex/jira/<Cloud-ID> For information on obtaining the value of Cloud ID, see [Obtain the value of Cloud ID](https://www.servicenow.com/docs/access?context=setup-jira-spk-opt2&version=australia&pubname=australia-integrate-applications&section=jira-cloud-id&ft:locale=en-US). 2. Select the credential type as 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. {#create-jira-tool-dev-ops__ol_hkb_nvb_rcc} 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://www.servicenow.com/docs/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."). 3. If your Jira instance is attached to a MID Server, select the MID Server option and enter its details. For more information about MID server, see [MID Server selection](https://www.servicenow.com/docs/access?context=c_MIDServerSelector&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) {#create-jira-tool-dev-ops__ol_tn5_klv_kbc} |
      |-|-|
      [ ]

      {#create-jira-tool-dev-ops__table_zld_3lv_kbc}
   2. Select Connect.  
      If the connection is successful, the tool is created in the DevOps Change Velocity and connected to your Jira instance.
   3. Permission checks are run on the credentials that you entered.  
      Permissions required and permissions that are available are displayed. If you want to enter credentials with better permissions, select Re-enter credentials. For detailed information on all the required permissions, see Jira permissions in [Permissions required for DevOps tools](https://www.servicenow.com/docs/rkQZOOxQSNdDZ7d5eHch0A "Permissions required in your third-party tool to connect to DevOps Change Velocity.").

      You can choose to continue with the tool connection even if you don't have all the required permissions.

   4. Select Next.
   {#create-jira-tool-dev-ops__substeps_wdp_x1b_fwb}
5. Specify the access for the tool.  
   1. If you want to control access to the tool, add the groups that must be given access to the tool in the Maintained by field.  
      The tasks these users in the groups can perform depends on the role assigned to them.
      * DevOps Tool Owner role: Can view and edit the tool.
      * DevOps App Owner role: Can view the tool and can associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects (such as plans, repositories, and pipelines).
      * DevOps Administrator role: Can edit all tools.
      * Other DevOps roles: Can view the tool.
      {#create-jira-tool-dev-ops__ul_csp_h5c_xwb}  
      Note:  
      If you don't select a group and skip this step, all users with the DevOps Tool Owner role will be able to edit the tool.
   2. If you choose to control access to the tool, the All App Owners can view and associate tool objects to applications option becomes available for selection.

      This option enables all users having
      the DevOps App Owner role to access the tool. If selected, they'll be able to view, associate, discover, import historical data, and modify pipeline steps (if applicable) of the tool's objects.
   3. Select Assign.

   {#create-jira-tool-dev-ops__ol_slg_2tz_cxb}
6. To send data in real time between DevOps and your Jira instance, select Configure.  
   This action does the following:
   * Registers a webhook between your Jira and ServiceNow instances, and enables real-time data transfer between the two.
   * 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. If you choose to configure the webhooks manually for a Jira tool created using OAuth 2.0 based authentication, a duplicate webhook may get created.
   {#create-jira-tool-dev-ops__ul_k4d_sbb_fwb}

   All the discovered Jira projects are listed as Plans.

   If you don't choose to configure now, you can enable nightly polling later to fetch data for any tracked plans by setting the Enable Polling system property to Yes.

   To configure manually, select Configure manually. See [Configure webhooks in Jira manually](https://www.servicenow.com/docs/P0oTPfK5lwJN3NKXtEZ3Vg "Configure webhooks in your Jira Server or Jira Cloud instance to send sync notifications to the DevOps Change Velocity application.") for more information.  
   Important:  
   * If you're connecting from the Home page or Tools module, the connection is complete and you're taken to the Summary page.
   * If you're connecting from the Applications module, then plans available in your Jira instance are discovered. You can track and import historical data from them.
   {#create-jira-tool-dev-ops__ul_yfy_zz1_bzb}
7. Select the plans to track.  
   1. Select the plans for which you want to track updates and associate to the application.

      After the tool onboarding is complete, the work items only for these selected plans are automatically imported.
   2. Select Next.

   3. If you want to import plan data, select the date range and select Submit.

      You can import up to 90 days of data.

   {#create-jira-tool-dev-ops__ol_zlk_1jc_bzb}
8. From the Summary page, select View tool record to review the details of the connected instance and the plans discovered from it.  

## Result

You've successfully onboarded your Jira tool to DevOps Change Velocity.

## What to do next

From the tool record page, you can:  
* See the details and status of the tool.
* Discover plans and Configure webhooks.  
  Note:  
  * By default, projects are discovered in a set of 50 for Jira Cloud. 50 is the maximum pagination limit supported by Jira. If you want to reduce this value, then you should edit the respective constant in DevOpsCommonConstants script.
  * Project and version data that are discovered aren't updated or tracked in real time.
  {#create-jira-tool-dev-ops__ul_xmz_5mh_kcc}
* Assign groups to control access to the tool using the Maintained by field.
* Check credential permissions and update credentials for the tool. For more details, see [Check permissions and update credentials for tools --- Workspace](https://www.servicenow.com/docs/SnNYbhNsgmuiHgktku9gNA "You can perform permission checks and update credentials like passwords and access tokens for your tools from the tool details page.").
* From the Plans tab, select a plan to view its details such as imported work items, features, and others.
* To import historical data from the plans, associate the plans with an application, and import the data. For more information, see [Associate tool objects to applications - Workspace](https://www.servicenow.com/docs/d~RLHHIdnkfXhP1np3FsoQ "After creating an application, you can associate plans, repositories, and pipelines with it. Applications group plans, repositories, and pipelines from DevOps tools, which provides traceability to user stories, commits, test results, and so on.").
{#create-jira-tool-dev-ops__ul_unf_ftx_5wb}  
Note:  
It is recommended not to update the project key for projects in Jira. If the project key is updated, the updated object names will not reflect in DevOps Change Velocity. Only when the object is updated in Jira, the new name will reflect in DevOps Change Velocity.
* **[Connect a Jira tool using OAuth 2.0 with 3LO](https://www.servicenow.com/docs/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.

**Related tasks**   

* [Configure webhooks from the tool record](https://www.servicenow.com/docs/xBCT3l6udjf2J51Iy9PfSw "Configure webhooks from the tool record to send data to DevOps Change Velocity after your tool is connected.")

*[\>]: and then