Problem
After integrating Azure DevOps to Jira, the list filter for Azure repositories returns empty.
Diagnosis
The integration status is INDEXED but users still see a blank list on the Manage repositories list with MS Azure list filter set.
Solution
If the integration is using the oAuth access, switch to personal access token instead. Also check PAT configuration when Creating Personal Access Tokens.
If the problem still persists, follow the solutions outlined in the following articles:
-
OAuth connection error or error 401 page with Azure DevOps integration
-
OAuth connection error or error 401 page with Azure DevOps with Active Directory integration
If you still have a question – reach out to our Support Desk or email us at [email protected].
Related articles
Why don’t I see commits? (Git Integration for Cloud) (Git Integration for Jira Cloud)
Repositories missing from Azure DevOps (or VSTS) integration (Git Integration for Jira Cloud)
Licensing error – installCheck failed (Git Integration for Jira Cloud)
Why don’t I see the Create branch or pull request features? (Git Integration for Jira Cloud)
Connection error for self-hosted git servers (Git Integration for Jira Cloud)
SSH key file format is invalid (Git Integration for Jira Cloud)
Error while reindexing – Java heap space / Object too large, rejecting the pack (Git Integration for Jira Cloud)
OAuth connection error or error 401 page with Azure DevOps integration (Git Integration for Jira Cloud)
OAuth connection error or error 401 page with Azure DevOps with Active Directory integration (Git Integration for Jira Cloud)
Empty list of repositories after integration of Azure Repos (this page)
