New reports+12%
47Last 7 days
Bug reports that arrive with the screenshot
bogR is a report widget for React apps and a hub that collects what it sends. Your users press one button, mark up a screenshot of the page and send it. Your team triages it in one inbox.
Try it on a pretend dashboard
Below is a stand-in bug-report app with the widget mounted. Find something wrong, report it, and it lands in this hub's Demo project.
- Open14
Not triaged yet
- Median time to triage42 min
Last 30 days
- Fixed this week+39
Closed as fixed
Reports per day
| Day | New reports |
|---|---|
| Mon, Oct 5 | 4 |
| Tue, Oct 6 | 6 |
| Wed, Oct 7 | 3 |
| Thu, Oct 8 | 7 |
| Fri, Oct 9 | 9 |
| Sat, Oct 10 | 5 |
| Sun, Oct 11 | 2 |
| Mon, Oct 12 | 5 |
| Tue, Oct 13 | 8 |
| Wed, Oct 14 | 6 |
| Thu, Oct 15 | 11 |
| Fri, Oct 16 | 7 |
| Sat, Oct 17 | 4 |
| Sun, Oct 18 | 6 |
On triage duty
This week's new reports are assigned to them.
Screenshot storage7.9 GB free
12.1 GB of 20 GB used
Everything a useful report needs
The reporter spends ten seconds, and you get the page, the browser and a picture of the problem.
The page, already captured
The widget renders the page from its DOM, or takes the tab through the browser's own capture, and attaches the image before the reporter types a word.
Marked up, not described
Boxes, arrows and a pen point at the problem. A black box hides what should not be seen, burned into the image before it leaves.
Private by default
Fields marked data-bogr-mask are blanked and elements marked data-bogr-ignore are left out. The reporter sees what is sent and can keep their details back.
One inbox per project
Status tabs, filters, search and assignees, with a timeline of every change and comment on each report.
A webhook on arrival
Each new report is posted to the URL its project names, and the answer shows on the report's timeline.
Kept as long as you say
Each project sets how long its reports are kept. A daily purge empties older ones to a tombstone.
From a bug to the inbox in three steps
The widget never talks to the hub itself: your server adds the key and the signed-in reporter.
Mount the widget
Wrap your React app in BogrProvider and put BogrButton in it.
Route it through your server
createBogrHandler sends each report on with the project's server key and the reporter your session knows.
Triage it in the hub
Reports land in the project's inbox with the screenshot, the page and the browser they came from.
providers.tsxtsx
Common questions
What happens to a report, and to the data in it.
No. It posts to a route on your own server, which adds the signed-in reporter and the project's server key, then sends the report on. The key never reaches the browser.