Last updated: March 2026
This page documents known issues and limitations in Git Integration for Jira Cloud along with available workarounds.
| Issue area | Affected scope | Impact | Workaround status |
|---|---|---|---|
| Repository and object size limits | Large integrations or repositories | Performance or data limits | Documented workaround available |
| Smart Commits attribution or duplicate commands | Smart Commit processing | Incorrect attribution or duplicate command handling | Use the documented API or processor choice |
| Microsoft integration edge cases | Azure DevOps or Microsoft integrations | PAT or pull-request behavior issues | Configuration workaround available |
| SSH automation limits | Single SSH repositories with Automation for Jira | Automation triggers do not run | Use HTTPS instead |
| Web-linking and UI issues | Plain Git integrations or sidebar rendering | Delayed updates or stale links | Re-enable integration or wait for Atlassian-side fix |
On this page:
- Repository limits per integration
- 2GB object size limit
- Smart commits user search issue
- Microsoft pull request status updates
- Microsoft PAT organization permission
- SSH repository automation triggers
- Tag loading timeout
- Left sidebar loading delay
- Duplicate Smart Commit commands
- Web links not updating
Repository limits per integration
Git Integration for Jira Cloud limits the number of connected repositories per integration:
| Git Service | Maximum Repositories |
|---|---|
| GitHub | 10,000 |
| GitLab | 10,000 |
| All others | 10,000 |
Reference: GITCL-1395, GITCL-1846
2GB object size limit
Git Integration for Jira uses the JGit library, which does not support objects over 2GB in size stored in git repositories.
Workaround: Remove large objects from repository history or use Git LFS for large files.
Smart Commits user search issue
Some users have smart commits attributed to the app user rather than specific users when user search via email fails.
Workaround: Use the assignable users API endpoint:
/rest/api/2/user/assignable/search?issueKey=ABC-123Reference: GITCL-800
Microsoft pull request status updates
Microsoft integrations require all pull requests for configured repositories to be requested each time for status updates. Microsoft’s Pull Request APIs do not provide filtering by last changed date/time.
Reference: GIT-3889
Microsoft PAT organization permission
IMPORTANT
When creating personal access tokens (PAT) for Microsoft/Azure integrations, select All accessible organizations. Otherwise, the integration will not work.
See Creating Personal Access Tokens for instructions.
For more information, see the official Azure DevOps PAT documentation.
Reference: GIT-3978
SSH repository automation triggers
Automation for Jira triggers work with auto-connected integrations and single HTTPS authenticated git repositories, but single repositories authenticated via SSH are not supported by Atlassian Jira Cloud.
See Atlassian bug: JSWCLOUD-20935
Workaround: Use HTTP/HTTPS connections for single repository git URLs:
| Connection Type | Example | Trigger Support |
|---|---|---|
| SSH (not supported) | [email protected]:admin/repo.git |
❌ |
| HTTPS (supported) | https://github.com/admin/repo.git |
✅ |
Reference: GITCL-1624
Tag loading timeout
Loading tags on integrations with large git history can take a long time. Git Integration for Jira Cloud limits tag loading to 10 seconds before timing out.
Left sidebar loading delay
The Git Integration for Jira app panel in the left sidebar takes up to 10 seconds to load.
Atlassian has opened a bug ticket for this issue.
Duplicate Smart Commit commands
When both Atlassian and GitKraken Smart Commit processors are enabled, users see duplicate #comment and #time commands.
| Processor | Commands Supported |
|---|---|
| Atlassian | #comment, #time, #<transition> + workflow triggers |
| GitKraken | #comment, #time, #<transition>, #assign, #label |
Recommendation: Use Atlassian processor (default) for workflow trigger support. Use GitKraken processor only if you need #assign and #label commands.
Reference: GITCL-1334
Web links not updating
In rare cases, web links for branches and tags do not update automatically after modifying the web-linking template.
Workaround:
- Temporarily disable the affected Plain Git integration.
- Re-enable the integration to apply the web linking update.
Reference: GITCL-3981
