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

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Bitbucket

# Bitbucket integration with DevOps Change Velocity {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 Minuten Lesedauer

Connect to your Bitbucket instance to track Bitbucket repositories, commits, branches, and pull requests.

## Bitbucket integration overview {#bitbucket-integration-dev-ops__section_ppq_dlx_t2c}

DevOps Change Velocity supports the Code (Repository) capability for the Bitbucket tool.

## Authentication methods {#bitbucket-integration-dev-ops__section_pnd_mlx_t2c}

You can connect to Bitbucket Cloud using one of the following authentication methods:

Basic Auth
:
    When you select the credential type as Basic Auth the repositories for all the workspaces in the organization are discovered. You can get the user name and password for Basic Auth from the settings of your Bitbucket account. To copy the user name, navigate to Settings \> General \> Account settings, and copy the user name from the Bitbucket profile settings section. To copy the password, navigate to Settings \> Personal Bitbucket settings \> App passwords, and select Create app password. Enter the necessary details and select the required permissions, and then select Create, and copy the password. The following permissions must be selected while creating the credentials:

    * Account: Read
    * Projects: Read
    * Webhooks: Read and write
    * Pull requests: Read

    {#bitbucket-integration-dev-ops__ul_ltr_ymx_t2c}

OAuth 2.0 - Authorization Code
:   You must create the OAuth consumer in the Bitbucket tool with the required permissions before creating the OAuth record for Authorization Code. You can navigate to Workspace settings \> OAuth consumers \> Add consumer in Bitbucket to add the OAuth consumer. Select the following permissions for the OAuth consumer.

    * Account: Read
    * Projects: Read
    * Webhooks: Read and write
    * Pull requests: Read

    {#bitbucket-integration-dev-ops__ul_wqm_cbm_52c}  
    Ensure that the This is a private consumer option isn't selected. You must enter your ServiceNow instance URL in the Callback URL field in the following format.

        https://<instanceurl>/oauth_redirect.do


    You can create an OAuth 2.0 - Authorization Code credential by performing the steps specified in the [Set up OAuth 2.0 Authorization Code for Bitbucket Cloud](https://servicenow-prod.fluidtopics.net/taHUoXBT9oFk3uXg9ymYDw "Set up OAuth 2.0 Authorization Code credentials for Bitbucket in DevOps Change Velocity to use a more secure authentication method.") procedure.
:
    Hinweis:  
    When you select the credential type as Oauth 2.0 - Authorization Code for Bitbucket Cloud, the repositories for all the workspaces are discovered. This is a limitation from Bitbucket side

OAuth 2.0 - Client Credentials
:   You must create the OAuth consumer in the Bitbucket tool with the required permissions before creating the OAuth record for Client Credentials. You can navigate to Workspace settings \> OAuth consumers \> Add consumer in
    Bitbucket to add the OAuth consumer. Select the following permissions for the OAuth consumer.

    * Account: Read
    * Projects: Read
    * Webhooks: Read and write
    * Pull requests: Read

    {#bitbucket-integration-dev-ops__ul_ms1_nbm_52c}  
    Ensure that the This is a private consumer option is selected as well. You must enter your ServiceNow instance URL in the Callback URL field in the following format.

        https://<instanceurl>/oauth_redirect.do

    You can create an OAuth 2.0 - Client Credential record in the workspace UI while onboarding the tool. You need the Client Id and Client secret values of your Bitbucket workspace. Client ID of your Bitbucket tool is available in the OAuth consumers section of your workspace settings (Workspace settings \> OAuth consumers \> Add consumer) in the Key field.
    Client secret of your Bitbucket tool is available in the OAuth consumers section of your workspace settings (Workspace settings \> OAuth consumers \> Add consumer) in the Secret
    field.

Access Token
:   You can create the access token by performing the steps specified in the [Atlassian](https://support.atlassian.com/bitbucket-cloud/docs/create-a-workspace-access-token/) documentation. Ensure that the following permissions are provided while creating the access token:

    * Account: Read
    * Projects: Read
    * Webhooks: Read and write
    * Pull requests: Read

    {#bitbucket-integration-dev-ops__ul_xhh_tcr_52c}

    You also need the workspace ID of your Bitbucket workspace. Copy it from the Workspace ID field in the Workspace settings of your Bitbucket Cloud account.

## Get started {#bitbucket-integration-dev-ops__section_f2g_clx_t2c}

Use one of the following options to onboard Bitbucket. For a guided experience, use the workspace to onboard a tool. Alternatively, you can use the Service Catalog or Classic experience.
* **[Onboard Bitbucket to DevOps Change Velocity --- Workspace](https://servicenow-prod.fluidtopics.net/T17zirDzl4sAgfuuEVrVSg)**   
  Create, connect, discover, and configure your Bitbucket instance using the DevOps Change Velocity workspace.
* **[Onboard Bitbucket to DevOps Change Velocity --- Service Catalog](https://servicenow-prod.fluidtopics.net/riBOoUx0ZqKdcBLRLM4nqg)**   
  Create, connect, discover, and configure your Bitbucket instance using the ServiceNow Service Catalog.
* **[Onboard Bitbucket to DevOps Change Velocity --- Classic](https://servicenow-prod.fluidtopics.net/YxaNN73LPPZsMUI6zOA1aw)**   
  Create, connect, discover, and configure your Bitbucket instance using the Classic UI.