A useful GitHub issue starts with more than a bug title. Gleap sends customer reports to the repository you choose, carrying the report and its captured technical context into your engineering backlog.
From customer report to GitHub issue
Create an issue from an individual ticket, or automatically forward selected ticket types. The integration supports creating and updating issues and sending messages to an issue, so new information can follow the original report.
For example, your support team can send a confirmed checkout bug to the repository that owns checkout while keeping routine account questions in Gleap.
Connect your repository
- Add GitHub from your project’s Integrations settings and authorize the connection.
- Choose the destination repository.
- Select which ticket types to send automatically, or leave automatic sending off for manual handoffs.
- Send a sample report and check that it reaches the intended repository with the context your team needs.
The issue tracker setup guide covers routing and connection checks. In-app bug reporting explains the evidence Gleap can capture before a report reaches GitHub.
When the next step is code
This integration puts work in GitHub Issues. Kai Code connects customer issues to implementation, helping your team turn bugs and requests into shipped fixes and features.
