Move a customer report into Azure DevOps with the context needed to start work. Gleap creates work items in your chosen project, giving teams that plan in Azure Boards a direct handoff from support. Work items and Kai Code are both available on Team, Pro and Enterprise.
Set the destination and work item type
Choose the Azure DevOps organization, project, and work item type. That lets a reported defect enter the process your team already uses, instead of arriving as an unstructured message someone must turn into work later.
The integration supports creating and updating work items and sending messages to them. Automatic routing is based on the ticket types you select; individual tickets can also be sent manually.
Before you connect
Your Azure DevOps organization must allow third-party application access. Gleap prompts you to check this policy before starting authorization.
- Add Azure DevOps in your project’s Integrations settings.
- Complete authorization and select the organization and project.
- Choose the work item type and configure forwarding.
- Test with a report whose ticket type matches your rule.
Read the issue tracker connection guide for routing and troubleshooting.
In-app bug reporting supplies the customer evidence. Your team decides how that evidence becomes planned work in Azure DevOps.
Pull requests from Kai Code
From Team, Kai Code also works in Azure Repos. Connect a repository in Kai Code and authorize Azure DevOps. Sessions on Kai Code Cloud and on the Kai Code Bridge, which runs on your own machine, open a pull request in the connected repository for your team to review and merge.
FAQ
Which Gleap plan includes the Azure DevOps integration?
Team, Pro and Enterprise include the work item integration and Kai Code, which works in Azure Repos. See pricing for the plans.
Does Kai Code open pull requests in Azure DevOps?
Yes. Kai Code opens a pull request in the connected Azure DevOps repository, on Kai Code Cloud and on the Kai Code Bridge, for your team to review and merge. It never merges on its own.
What does our Azure DevOps organization need before we connect?
Third-party application access must be allowed in your organization policies, or Gleap cannot connect to your projects. Gleap reminds you to check this policy before authorization starts.
