Gleap was originally built to be a bug reporting tool, which is why we believe that we’re still amazingly good at helping both users report bugs easily and dev teams deal with issues in minutes. Gleap whips visually and technically complete reports with every issue a user creates; and if there are still open questions, you can chat with your users in real time to figure things out.
1. Organize, assign and prioritize
All bugs land in one organized kanban board. In every report you can then assign the bug to the responsible person, change its priority and even give it a due date. Additionally, you can communicate with your users directly within the ticket and send notes to team mates, too.
2. User data
With every report you also get the user data with information such as name, email and location. By clicking on a user, you get all the conversations with that user at one glance. If you want you can also set a value for a user so you can prioritize issues depending on pricing.
3. Meta data
In the meta data you can find the screen size, the device as well as the browser information of the user behind the reported bug.
4. Visual feedback: screenshots and replay videos
With every bug report we send an annotated screenshot so you no longer have to guess where the error occurred. If you choose to, Gleap also ships replay videos to reproduce an error in seconds - with those replay videos you can literally watch bugs happen. If for data protection reasons, you don’t want to collect visual data you can simply turn it off in the settings.
5. Console & network logs
Every report comes with console and network logs. Sometimes they contain all the secrets. Never miss the important information when a bug happens.
6. Custom data
With a little bit of extra coding, you can collect custom data. This is especially useful if you have certain events that you would like to track.