Git Integration for Jira incident
Microsoft OAuth integrations not indexing on Dev Info for Jira
Resolved after 24 days 17 hours, affecting Git Integration for Jira Cloud - Global Region, on June 25, 2023.
A fix has been implemented. Customers who use the the OAuth integration type for Microsoft Azure Repos or Microsoft VSTS will need to reconnect. See https://help.gitkraken.com/git-integration-for-jira-cloud/reconnecting-azure-devops-and-vsts-oauth-integrations-gij-cloud/ for instructions on how to reconnect.
Affected components
Update timeline
- identified Jun 25, 2023, 11:16 AM UTC
Microsoft VSTS and Azure DevOps OAuth applications have a bug/limitation where the application secret expires 5 years after creation. This secret cannot be refreshed/updated. The workaround from Microsoft is to create a new OAuth application and have consumer re-connect: https://developercommunity.visualstudio.com/t/client-secret-is-expired-even-after-refresh/1564908 We will be updating production shortly. Once updated, customers will need to reconnect https://cln.sh/26TUNm in the integration settings. If you need assistance with this, please contact [email protected]. The application affected is Dev Info for Jira: https://marketplace.atlassian.com/apps/1219270/dev-info-for-jira?tab=overview&hosting=cloud
- identified Jun 25, 2023, 11:16 AM UTC
We are continuing to work on a fix for this issue.
- monitoring Jun 25, 2023, 11:17 AM UTC
A fix has been implemented. Customers who use the the OAuth integration type for Microsoft Azure Repos or Microsoft VSTS will need to reconnect. See https://help.gitkraken.com/git-integration-for-jira-cloud/reconnecting-azure-devops-and-vsts-oauth-integrations-gij-cloud/ for instructions on how to reconnect.
- resolved Jul 20, 2023, 04:27 AM UTC
This incident has been resolved.
Your product runs on more than Git Integration for Jira
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services