{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":32214,"path":"it-service-management/devops-change-velocity/sc-jira.md","title":"Onboard Jira to DevOps Change Velocity — Service Catalog","bundle":null,"doc_type":null,"release":"australia","body":"\n# Onboard Jira to DevOps Change Velocity — Service Catalog\n\nCreate, connect, discover, and configure your Jira Server or Jira Cloud instance using the ServiceNow Service Catalog.\n\n## Before you begin\n\nRole required: sn\\_devops.admin or sn\\_devops.tool\\_owner\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Service Catalog** &gt; **Catalog Definitions** &gt; **Maintain Items** and search for DevOps.\n\n    **Note:** You can also access the service catalog from the Employee Center or Service portal.\n\n2.  From the DevOps catalog items, select and activate **DevOps App Onboarding** and **DevOps Tool Onboarding**.\n\n3.  After activating, select **DevOps Tool Onboarding** and select **Try it**.\n\n4.  In the DevOps Tool Onboarding form, enter the tool details:\n\n<table id=\"table_bsr_hkv_kbc\"><tbody><tr><td>\n\nJira Server\n\n</td><td>\n\n1.  In the **Tool name** field, enter a name for the tool.\n2.  In the **Tool integration** field, search for and select Jira.\n3.  Enter your Jira server instance URL.\n4.  From the **Credential type** list, select the authentication type you want to use to connect with your Jira server.\n    -   **Basic Auth**\n\n        1.  Enter your Jira server username.\n\n**Note:** The Jira user that you use here must have the Jira Administrators permissions.\n\n        2.  Enter the password or access token to access this instance.\n    -   **API Key**\n\nEnter the API token to access the instance.\n\n5.  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?**\n6.  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.\n\n\n</td></tr><tr><td>\n\nJira Cloud\n\n</td><td>\n\n1.  In the **Tool name** field, enter a name for the tool.\n2.  In the **Tool integration** field, search for and select Jira Cloud.\n3.  in the **Tool URL** field, enter your Jira Cloud instance URL.\n4.  In the **Credential type** field, select **Basic Auth** or **OAuth 2.0 with 3LO**.\n\n**Basic Auth**\n\n    1.  Enter your Jira Cloud username.\n\n**Note:** The Jira user that you use here must have the Jira Administrators permissions.\n\n    2.  Enter the password or access token to access this instance.\n**OAuth 2.0 with 3LO**\n\nSelect the OAuth credential record. For more information, see [Connect a Jira tool using OAuth 2.0 with 3LO](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/connect-a-jira-tool-using-oauth-2-0-with-3lo.md).\n\n5.  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?**\n\n**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.\n\n6.  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.\n\n\n</td></tr></tbody>\n</table>    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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/tool-req-permission.md).\n\n5.  Select **Order Now**.\n\n    A request is created. When the request is approved, the tool is created, connected, configured, and discovered.\n\n6.  From the DevOps catalog items, select **DevOps App Onboarding** and select **Try it**.\n\n7.  In the DevOps App Onboarding form, enter the details:\n\n<table id=\"table_vb5_s3p_gwb\"><tbody><tr><td>\n\nAre you creating a new app or adding to an existing one?\n\n</td><td>\n\nSelect from the options whether to create a new app or use an existing app.\n\n</td></tr><tr><td>\n\nApp\n\n</td><td>\n\nEnter the name for the app that you're creating or using.\n\n</td></tr><tr><td>\n\nOnboarding pipelines\n\n</td><td>\n\nLeave empty.\n\n</td></tr><tr><td>\n\nOnboarding repositories\n\n</td><td>\n\nLeave empty.\n\n</td></tr><tr><td>\n\nOnboarding plans\n\n</td><td>\n\nEnter the connected Jira tool name.\n\n</td></tr><tr><td>\n\nPlans\n\n</td><td>\n\nSelect the plans for which you want to import historical data.\n\n</td></tr><tr><td>\n\nImport from and Import to\n\n</td><td>\n\nSelect 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.\n\n</td></tr></tbody>\n</table>8.  Select **Order Now**.\n\n    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.\n\n\n**Parent Topic:**[Jira integration with DevOps Change Velocity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/devops-change-velocity/jira-integration-dev-ops.md)\n\n"}}