On this page, you will be able to setup your git repositories and connect them to Jira.
On the Add new integration page, the list of supported Git host services is displayed.
Click on the git host service that you will be working on and connect it into Jira.
Git Integration for Jira app supports one or more integration types for specific Git host service:
-
Git service integration – supports automatic connecction and iconfiguration of integration repositories using your Git service account or PAT.
-
Plain Git integration – manually connect single HTTP/HTTPS or SSH git repositories into Jira. See supported Remote Git URL examples on the connection wizard.
Git service integration
RECOMMENDED
The following are types of integration supported by Git Integration for Jira app for automatic connection of specific git host service:
- OAuth Git service integration
- PAT Git service integration
- Webhook indexing integration*
See example integration support table for popular git host services:
Git host service | OAuth integration | PAT integration | Webhook indexing |
---|---|---|---|
GitHub | |||
GitLab | |||
Azure Repos/VSTS | |||
Azure DevOps/TFS | |||
AWS CodeCommit | |||
Gerrit | |||
Bitbucket |
OAuth integration
Formerly known as Full feature auto-connect integration.
Use this type of integration to connect specific git host services to Jira. This integration supports multiple connected repositories and automates most git integration settings.
For more details on supported git host services, see the full feature integration section in our Integration Guides.
PAT integration
This type of iintegration has similar features to OAuth but uses PAT (personal access token) instead to automatically connect repository integrations.
Support for Gitlab API v3 is deprecated. We recommend to use GitLab API v4 when adding new integrations for increased security.
Webhook indexing integration
Connect directly to a Git service by configuring webhooks to push commit, branch, pull request, and tag data to Jira Cloud.
Webhook indexing integration allows your connected git servers to work behind a firewall. However, the downside is that your integration will have limited features. For now, the supported git servers are GitHub.com, GitLab and Microsoft. More will be coming in the future.
Plain Git integration
Manually connect single git repositories using this setup such as git protocol, SSH, HTTP/HTTPS, etc. or simply connect one specific repository.
Connected git service integrations appear in the Manage integration configuration list.
-
Use the search option and filter to control integration list display.
-
Use the checkbox to specifically select integration/repositories from the list. Pair this with actions to perform multiple configuration for selected items.
-
Use the column headers to sort the list in ascending or descending order.
-
Use Actions to manage integration/repository settings.
The above UI descriptions also apply to the Manage repositories page since it has a similar layout.
Reindex selected (formerly Reindex All)
UPDATED FEATURE
In the new managed user interface, the Reindex all function is further improved and superseded by (1) selecting one or more integration/repositories using the checkboxes on the Manage integrations list, and then (2) performing reindex on the selected items.
This function will perform a reindex queue of all the selected integration/repository from the list.
Reindex is not available on DISABLED integrations or repositories. On multiple item selection, Reindex will ignore DISABLED integrations or repositories. For more information on this topic, see Reindexing.
More features
Click the … to see more features such as Repository browser and General settings.
The rest of the features can also be accessed on the left sidebar of the Manage integrations page.