Supported Git providers
|
Provider |
Cloud support |
Notes |
|---|---|---|
|
Gerrit Code Review |
Available |
Full support. Configure via Jigit admin page > Gerrit tab. |
|
GitHub Cloud |
Available |
Supports Personal Access Token (PAT) and GitHub App authentication. |
|
GitLab Cloud |
Roadmap |
On our roadmap. Migrated configurations from Data Center are preserved in Cloud with an Unsupported status and will activate automatically when support is added. |
|
Azure DevOps |
Not available |
We recommend Azure DevOps for Jira, which is purpose-built for Azure DevOps and Jira Cloud integration. |
If you use Azure DevOps and are migrating to Jira Cloud, see the Azure DevOps for Jira documentation for setup instructions. Your Azure DevOps configurations will be preserved during Jigit migration but will not be active.
Feature comparison: Data Center vs Cloud
The table below summarises which Data Center features are available in Jigit Cloud today, which are planned, and which are not applicable to the Cloud environment.
|
Feature |
Data Center |
Cloud |
Notes |
|---|---|---|---|
|
Pull request indexation |
Yes |
Yes |
PRs linked to Jira work items appear in the Jigit Development panel on the issue view. |
|
Branch indexation |
Yes |
Yes |
Branches linked to Jira issues appear in the Jigit Development panel. |
|
Commit indexation |
Yes |
Not available |
Cloud does not support commit-only indexation. Integrations migrated from DC with commits-only enabled are imported as disabled; enabling branches or PRs will reactivate them. |
|
Gerrit code review |
Yes |
Yes |
Gerrit changes appear in the Gerrit tab in the Jira issue Activity section. |
|
GitHub Cloud via PAT |
Yes |
Yes |
Personal Access Token connection works the same as DC. |
|
GitHub App authentication |
Yes |
Yes |
Recommended for GitHub Cloud connections. |
|
GitLab Cloud |
Yes |
Roadmap |
Configurations preserved on migration; will activate when support is added. |
|
Azure DevOps |
Yes |
Not available |
Use Azure DevOps for Jira instead. |
|
Webhooks |
Yes |
In progress |
Webhook settings are carried over during migration, but the webhook URL on your Git provider must be updated to point to the new Cloud endpoint after migration. |
|
Smart commits |
Yes |
Not available |
Smart commits (e.g. |
|
Create / link branch from Jira |
Yes |
Roadmap |
Only linking branches directly from a Jira issue is supported in Jigit Cloud at this time. |
|
Create / link code review from Jira |
Yes |
Not available |
Creating or linking code reviews from Jira is not supported in Jigit Cloud at this time. |
|
GitHub Dependabot alerts |
Yes |
Not available |
Dependabot alert configurations are project-level in DC and have no equivalent in Jigit Cloud. |
|
Activity report |
Yes |
Not available |
The Git activity report is a Data Center feature with no equivalent in Cloud at this time. |
|
Project-level configuration |
Yes |
Roadmap |
Cloud uses global-level configuration only. Project-level configs from DC are migrated to global scope. |
|
User-level Git credentials |
Yes |
Yes |
Jira users can manage their own Git connection credentials via Profile > Jigit Git Connections. |
|
Cloud Migration Assistant (CMA) |
Coming soon |
Coming soon |
Automated migration via Atlassian CMA is implemented but not yet available. See Jigit - Migrating from Data Center to Cloud. |
|
Manual JSON migration |
Coming soon |
Available |
Export JSON from DC admin, import in Cloud admin Migration tab. See Jigit - Migrating from Data Center to Cloud. |
For any questions regarding supported functionality, please contact us via our Support Portal.
Updated: