Known Issues
The Git Integration for Jira app is packed with features that makes Jira administrators and developers happy. However, with different hardware configurations out there, these great features can also become burdened by issues.
Below are the Git Integration app known issues and workarounds:
- 1 2GB Object Git Repositories Storage Limit
- 2 Surpassing JQL 65K Jira Issues Searching Limitation
- 3 Commits Relating Only to Tags are Not Displayed
- 4 Fully Cancelling an Ongoing Indexing is Not Possible
- 5 Microsoft Pull Request Requirement for Status Updates
- 6 Why Microsoft PAT Integrations Require “All accessible organizations” Permission
- 7 Enabling the App With Many Repositories Configured
- 8 Pull Requests Changed Before Migration to v3.7 Do Not Trigger Workflow Hooks
- 9 Deleted Merge Requests Not Removed from the Jira Issue Screen
- 10 Azure DevOps: Long Pull Request Descriptions Limited to 400 Characters
- 11 Gerrit Integration Connected with Errors
- 12 Starred repositories Custom API Path might fail if using SSO
2GB Object Git Repositories Storage Limit |
Git Integration: Jira DATA CENTER The Git Integration for Jira application uses the JGit library which does not support objects over 2GB in size stored in git repositories.
Reference: … |
Surpassing JQL 65K Jira Issues Searching Limitation |
git integration: jira DATA CENTER To increase the 65,000 issue JQL search limit:
For more information on this issue, see Atlassian KB - 65K issue limit in JQL functions - Time to SLA for Jira. Please contact support@bigbrassband.com if you encounter related issues. Reference: GIT-3710, GITSERVER-1008 |
Commits Relating Only to Tags are Not Displayed |
GIT INTEGRATION: jira DATA CENTER During the commits indexing, the Git Integration app processes only branches. Thus, it only sees the commits belonging to any branch. However, if some commits relate only to tags, these commits will not be displayed. Affected example: Reference: GIT-3854 |
Fully Cancelling an Ongoing Indexing is Not Possible |
git integration: jira data center Cancelling indexing from the Git Integration admin interface is not currently possible. See Workaround. |
DISABLING A REPOSITORY OR INTEGRATION IN MANAGE GIT REPOSITORIES PAGE When a repository is disabled, the process is still ongoing while it skips indexing some of its entities. |
DISABLING THE GIT INTEGRATION FOR JIRA APP IN THE MANAGE APPS |
WORKAROUND Reference: GIT-3847 |
Microsoft Pull Request Requirement for Status Updates |
git integration: jira data center Microsoft integrations require all pull requests for the configured repositories to be requested each time for status updates. Microsoft's Pull Request APIs do not currently provide any information allowing for filtering by last changed date/time. Reference: GIT-3889 |
Why Microsoft PAT Integrations Require “All accessible organizations” Permission |
git integration: jira data center It is highly required that administrators must select the “All accessible organizations” option when creating personal access tokens (PAT). Otherwise, the integration will not work. Please follow the instructions for creating MS/Azure PATs outlined in our Confluence how-tos here. For more information, see the official reference for Azure DevOps PAT integration. Reference: GIT-3978 |
Enabling the App With Many Repositories Configured |
git integration: jira data center Repositories are initialized upon enabling the Git Integration for Jira app. This initialization process can take several minutes when many repositories are configured. We are working on an improvement to move this initialization process away from enabling/disabling the app. Reference: GIT-3977 |
Pull Requests Changed Before Migration to v3.7 Do Not Trigger Workflow Hooks |
git integration: jira data center Pull requests changed before migration to v3.7 do not trigger workflow hooks. Reference: GIT-3989 |
We strongly suggest that you perform a “Reindex All” in the git manager page after the app upgrade to v3.7+. |
Deleted Merge Requests Not Removed from the Jira Issue Screen |
git integration: jira data center The deleted merged requests are not removed as expected from the Jira Issue page after the app upgrade to v3.7+. Cause: GitLab’s API responses do not contain sufficient information about deleted merge requests when requesting updated merge requests. Reference: GIT-3989 |
WORKAROUND |
Azure DevOps: Long Pull Request Descriptions Limited to 400 Characters |
git integration: jira data center Azure DevOps supports descriptions of pull requests with the maximum length of 4000 chars in the web interface. However, only the first 400 characters of an Azure DevOps Pull Request description are made are made available via the Azure DevOps API. As a result, the long PR descriptions appear to be cropped in the tooltip over a pull request on the Git Integration panel. Reference: GIT-3989 |
Gerrit Integration Connected with Errors |
git integration for data center The standard Gerrit "All-Projects", "All-Users" and other parent repositories do not contain commits and JGit is not able to clone/index these repositories. WORKAROUND
Reference: GIT-4111 |
Starred repositories Custom API Path might fail if using SSO |
The Custom API Path, Error! |