Microsoft webhook indexing integration

With webhook indexing integration, there’s no need to enable indexing triggers in the git manager configuration page.

For a step-by-step setup guide, watch the following demonstration videos:

Connect Azure Repos, Azure DevOps, Azure DevOps Server, VSTS or TFS using the Webhook Indexing integration type to Jira Cloud:

The steps outlined below requires that Git Integration for Jira app is already installed on your Jira Cloud instance. Otherwise, install the Git Integration for Jira app first from the Atlassian Marketplace.

  1. Webhook indexing integration

    1. On your Jira Cloud dashboard, go to AppsGit Integration: Manage Git repositories.

    2. On the integration panel under Limited feature connect, click Webhooks.

    3. On the following screen, click Microsoft as your git server type.

    4. Click Connect Microsoft under Webhooks indexing column to connect to your git server. The following screen is displayed:

      • Enter a meaningful Display name for the new webhook indexing integration.

    5. Before clicking Finish, make sure to configure webhook for your git service. Follow the steps below for the webhook setup.

  2. Microsoft service hook setup
    Project level
    Open a new browser tab and login to your Microsoft web portal to setup webhook triggers for the selected project. Configure a webhook on your git service by performing the following steps:

    1. On your Microsoft web portal, open a project to work on.

    2. On the sidebar, go to Project Settings.

    3. Click Service hooks. The service hooks configuration page is displayed.

    4. Click Create subscription (If there are existing configuration in the list, click + to add a new subscription instead). The Service hook wizard is displayed.

    5. Select a service to integrate with by scrolling down to Web Hooks, click on it then click Next. The Trigger screen is displayed.

    6. Select an event to trigger on and configure any filters. We recommend to setup the following three (3) event triggers in separate webhook subscriptions:

      1. Code pushed

      2. Pull request created

      3. Pull request updated

    7. Set all FILTERS to any then click Next to continue. The Action screen is displayed.

    8. On the Settings URL box, paste the Webhook URL that you got from the previous section.

    9. important On the Settings Basic authentication password, paste the the Secret key from the previous section.

    10. Review your service hook setup and we recommend to test your settings. For example, test Code push event and Pull request events if it fails or succeeds.

    11. If it returns no errors, click Finish on this subscription wizard to save the service hook configuration.

    12. The service hook configuration is added to the service hook list.

    13. Create subscriptions for Pull request created and Pull request updated with the steps outlined in step 2 Microsoft service hook setup project level .

  3. Microsoft service hook setup
    repository level
    Open a new browser tab and login to your Microsoft web portal to setup webhook triggers for the selected repository. Do the steps similar to the project level setup but choose a repository instead (see step 3g.

    1. On your Microsoft web portal, open a project to work on.

    2. On the sidebar, go to Project Settings.

    3. Click Service hooks. The service hooks configuration page is displayed.

    4. Click Create subscription (If there are existing configuration in the list, click + to add a new subscription instead). The Service hook wizard is displayed.

    5. Select a service to integrate with by scrolling down to Web Hooks, click on it then click Next. The Trigger screen is displayed.

    6. Select an event to trigger on and configure any filters. We recommend to setup the following three (3) event triggers in separate webhook subscriptions:

      1. Code pushed

      2. Pull request created

      3. Pull request updated

    7. For FILTERS: to apply this trigger to a specific repository, select it from the Repository selector list and then click Next to continue. The Action screen is displayed.

    8. On the Settings URL box, paste the Webhook URL that you got from the previous section.

    9. important On the Settings Basic authentication password, paste the the Secret key from the previous section.

    10. Review your service hook setup and we recommend to test your settings. For example, test Code push event and Pull request events if it fails or succeeds.

    11. If it returns no errors, click Finish on this subscription wizard to save the service hook configuration.

    12. The service hook configuration is added to the service hook list.

    13. Create subscriptions for Pull request created and Pull request updated with the steps outlined in step 3 Microsoft service hook setup repository level .

  4. After you’re done setting up the service hook with your git service (Microsoft), switch to the Jira Cloud browser tab where you left off. Click Finish to complete this setup.

If you see any issues with the newly added service hook, verify that the Webhook URL from the Microsoft webhook indexing page is copied and pasted properly to the URL box in the Service hook wizard. Edit the these settings and try again.

Edit integration settings via Actions on the Manage Git repository page. In here, you will find Webhook URL and Secret key for use with service hook setup with your Microsoft git service.

Make a commit if you don’t see commits in the Git Commits tab of an associated Jira issue.

For information on this topic, see Linking git commits, associating branches and pull requests to a Jira issue.

Video Guide

Project Level

Right click here and open this video in a new window/tab for more viewing options.

Limited features for Microsoft webhook indexing integration

The feature table displays the supported git features for the selected git server. For more information, see Feature matrix for Git Integration for Jira Cloud.

Click View supported types below the table to see the currently supported git service types.

Works with git servers behind firewall

The webhooks indexing integration limits the features available. However, networks hosting git do not need to be updated to allow incoming requests as long as outbound requests can be made. See Webhook Indexing explainer for more information.

View commits, branches, pull requests in Jira

Commits, branches, pull requests are visible in the Jira Development Information panel as well as in the Git Commits issue tab and Git Integration side panel of the Jira issue. Jira administrators can regulate access to these displays using the View development tools permission.

Jira issue Git Roll Up tab
With Microsoft webhook indexing integration, the Git Roll Up tab only provides commit message and hashes, dates and author information. It does not offer information about changed files.

View tags in Jira

comming soon

Support for Automation for Jira + Smart Commits

Automation for Jira - the following triggers are supported:

  1. Commit created

  2. Branch created

  3. Pull request created

  4. Pull request declined

  5. Pull request merged

Smart Commits: Atlassian’s Smart Commits are enabled by default. Additional Smart Commit commands are available. See Smart Commits for more information.

Repository Browser

The Repository Browser allows users to view commits in git repositories by branch1. Users can manually link and unlink commits to Jira issues2.

  • Click a git repository on the View all repositories page to start from here.

Create branches and pull requests in Jira

This feature is not supported with webhook indexing integration. For more information, see Feature matrix of Git Integration for Jira Cloud

Support for large number of commits in git pushes

Git servers may truncate how much of the activity is captured in a webhook on large git push events resulting in some git activity. For more information, see Feature matrix of Git Integration for Jira Cloud.

Indexing full repository history

Webhook indexing integration will only show new commit/branch/pull request activity once webhooks are configured on the git server according to this wizard. For more information, see Feature matrix of Git Integration for Jira Cloud.

View source code in Jira

Webhook indexing integration does not have this option as webhooks do not contain source code.