Bug reports
Your users show you the bug. Blipit shows you the code.
A Report a bug button that sends a marked-up screenshot or a screen recording with voice, with the browser, page and errors attached.
Every plan, Free included
Explore Bug reportsReleases
Know whether the release you just shipped is healthy.
Adoption, crash-free sessions, deploys and the commits most likely behind a new error, for every release.
What it does
- 01
New and returning issues for each release.
- 02
Suspect commits from GitHub, and code owners per path.
- 03
Source maps, so minified errors point at your real code.
- Plan
- Every plan, Free included
- Works with
- Every stack
Up next
Keep exploring Blipit.
Service desk
Answer every report, and keep the reporter in the loop.
Reply to the reporter by email or in the Odoo chatter, talk with your team in internal notes, and attach the files that explain the fix.
Every plan, Free included
Explore Service deskError monitoring
Every error, from every stack, down to the line that broke.
Thousands of crashes become one issue per cause, mapped back to the file and line in your own code, with the release and the steps that led there.
Every plan, Free included
Explore Error monitoringYour next bug is already on its way.
Start on the Free plan. Add the SDK, the report button or the Odoo module, and your next bug arrives with the code that broke.