Git Integration for Jira Cloud Documentation

Contact support
GitKraken Status  

Adding webhooks for Azure DevOps Server | TFS

Pull request webhooks are now supported. See details on this page.

Supported webhook events:

  • Code pushed
  • Pull request created
  • Pull request updated
  • Pull request merge attempted


Right click here to open this video in a new browser tab for more viewing options. (While the above video showcases VSTS/Azure DevOps, the entire process is entirely the same for Azure Repos webhooks setup.)
Before you can proceed with the steps outlined on this guide, webhooks must be enabled in the Git Integration for Jira app repository configuration for your Jira instance. For more details, see Indexing triggers – Getting Started.


Setting up webhooks for Azure DevOps Server and TFS

Configure webhook by logging in to your Azure DevOps Server/TFS account.

  1. Open a project by clicking on it.

  2. Click Project Settings (sidebar) then select Service Hooks. The following screen is displayed.

    Click the icon to add a new service hook subscription.

  3. Scroll to Web Hooks and click to select it.

  4. Click Next. The following screen is displayed.

    • Set “code pushed” for the Trigger on this type of event selector.

    • Set all FILTERS to “Any”.

    • Click Next to proceed to the following screen.

  5. Switch to your Jira Cloud instance and navigate to Apps ➜ Git Integration: Manage integrations then click Indexing triggers on the sidebar.

    Copy the complete secret key URL using the copy icon on the right.

  6. Switch back to Azure DevOps Server/TFS (where you left off) and paste this information into the provided URL box.

  7. Click Test to verify if webhook integration is successful or not.

  8. Click Finish to complete this setup.


Pull request webhooks

The Git Integration for Jira app supports pull request webhooks now.

You will need to have three (3) separate service hooks configuration for it to work properly. Aside from setting up the “Code pushed” service hook outlined above in step 4.a, perform the same process with Pull request created and Pull request updated for the triggers.

Have feedback about this article? Did we miss something? Let us know!
On this page