Skip to main content
Skip table of contents

How to set up Azure DevOps integration?

Jigit - Jira GitHub & GitLab integration provides an issue view tab and development panel, which displays information about Azure DevOps commits, branches and pull requests referencing the Jira issue. Additionally, you can create new branches or pull requests directly from the Jira issue view.

Available since version 9.03.23.

Create Jigit Configuration

Before starting the Jira and Azure DevOps integration setup, you have to generate Personal Access Token on the Azure DevOps side.

How to create Azure DevOps personal access token?

Once your Access Token is ready you can move to the integration setup:

  1. On the Global or Project configuration page navigate to the Configurations tab.

  2. Click on Add new configuration.

  3. Indicate an alias (name) for your configuration which will be displayed on the commits tab page.

  4. Enter a host URL of your Azure DevOps Cloud instance or select from predefined values.

  5. Provide Personal Access Token you have generated on the Azure DevOps side.

  6. Add Path to the source code. It can be either a repository name (use the full repository path) or a repository group (use Azure DevOps organisation name or project path). Also, you have to specify the content type inside a given path: repository or a group of repositories (drop-down opposite the path).

For example, in the URL the name of the repo is Move-Work-Forward/BTR%20project/_git/MWF and the group name is Move-Work-Forward or Move-Work-Forward/BTR%20project.

To include all repositories in a group you need to use .* mask.

  1. After you have specified all the required parameters click on Ok button to save the configuration.

  2. Test Connection button allows you to check the connection and communication between Jira and the connected Azure DevOps instance.

Once the configuration has been created, you can start using the app on the Jira issue view screen. The other configurations are optional to make your integrations more streamlined and efficient.

Below you can find a short definition of the additional parameters you can specify:




Default Branch

The default branch of your Azure DevOps repository that will be used for integration with Jira; Jigit indexes git commits from the default branch and then from the others.

When you use Test Connection action, it uses the default branch and the first accessible repository to check the connectivity.

Jira Projects

Jira project names list where the commits and pull requests should be visible

Use only for Development panel

development activities from Azure DevOps will be shown only on the development panel.


a way of branch indexing:

  • all branches inside a repository;

  • selected branches;

  • branch mask helps filter and match specific branches in your GitHub or GitLab repository.

The aim is to decrease the number of API calls if this number is limited (it's actually for, for example). If you select the "all branches" option, Jigit makes API calls to check whether there have been new git commits since the last check (even to stale branches).

Enable smart commits

allows you to enable or disable the use of smart commits; Jigit support for smart commits for transition: if you write the commit message in the form #in-progress (hash, status name without spaces), the issue will be transitioned to the status In Progress. The smart commits work similarly to the Bitbucket Smart Commits.

It works only if your workflow does not have any mandatory fields on transition.

Ignore smart commits older than

lets you to specify a time duration after which smart commits should be ignored

Add git activities as issue comments

when enabled, Git activities, such as commits, pushes, and merges, are automatically added as comments to associated Jira issues.

After a commit is added, the operation can't be reversed. Comment stays there even if plugin is deleted.

Index pull requests

Jigit can index, pull request messages; when this parameter is enabled, the integration will actively monitor and index the pull requests in your repositories.

The pull request title should contain the issue key. For instance, DEV-123 added support for pull requests indexing for GitLab and GitHub.

Display repos in the development panel

the visibility of repositories to be able сreate a branch, link a branch to Jira issue, and сreate a code review using Jigit Development Panel.

Change default indexation settings

by enabling you can specify:

  • Commit indexing window a period within which commits are indexed and associated with Jira issues

  • Commit Request Timeout the maximum amount of time allowed for making a request to retrieve commit information from the connected GitHub or GitLab repository; this parameter is used when Jigit calls the git server by HTTP API, and if the timeout is exceeded during a call the add-on stops the indexing of a repository. If you see ConnectException: Connection timed out in JIRA logs, you can increase this value to overcome it. Default and recommended - 10 seconds.

  • Sleep the duration of a pause or delay between consecutive requests made by the integration to the connected GitHub or GitLab repository. Default and recommended - 10 seconds.

  • each frequency at which the integration checks for new commits or changes in the connected GitHub or GitLab repository Default and recommended - 100 requests.

How to link Git entities to Jira issues?

How to create a pull or merge in Jira using the Jigit app?

How to create a feature branch in Jira?

How to link the branch to the Jira issue?


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.