Why most bug reports can't be reproduced
The people who find bugs on a client's website are rarely the people who fix them. Clients, their staff and their customers notice when something breaks, but they don't know what a console is, and shouldn't have to.
So reports arrive missing exactly what a developer needs: the page, the browser and version, the screen size, what was clicked before, and the error that fired. Reproducing the bug takes longer than fixing it, and some never get reproduced at all.
A good bug report collects that context automatically, at the moment the reporter sends it, without asking them to do anything technical.
How it works
How to do it with Scopepin
- 1
Install the widget
Add one line to the site. It records console lines, errors and failed requests from the moment the page loads, and keeps a short replay in memory.
- 2
Someone reports a bug
They click Feedback, click the broken thing and describe it. They can draw on the page or record their screen to show what happened.
- 3
You see what happened
Open the report for the snapshot with the pin on the element, the browser and screen, the console and failed requests, and a replay of the minute before they sent it.
- 4
Fix and close the loop
Assign it, send it to your task tool, and mark it resolved. You can email the reporter when it's fixed.
What helps
Console errors and failed requests
JavaScript errors and failed network calls from the page, timed against the report.
Session replay
A replay of what the reporter did in the minute before sending, with form fields masked. Played back without running the page's scripts.
A snapshot at their screen size
The page rebuilt as they saw it, with the pin on the element and their drawings on top.
Anyone can report
No login, no extension. Reporters are free and unlimited on every plan.
Example
A client's customer reports “the checkout button does nothing”. The report shows Safari on an iPhone, a failed request to the payment endpoint with a 403, and a replay where the button is tapped three times. You find the blocked domain in two minutes and fix it the same afternoon, without a single follow-up question.
What a useful bug report includes
- Where it happened: the page and the element.
- What was expected, and what happened instead.
- The environment: browser, version, system and screen size.
- What came before: the clicks and inputs that led to it.
- The evidence: console errors, failed requests, a screenshot or recording. The best tools collect this part for the reporter.
Questions
Does it slow the site down?
The widget loads after the page. The snapshot code loads only when someone sends a report, and the replay recorder starts once the page has settled.
Is personal data captured?
Form fields are masked in snapshots and replays, and cookies aren't collected. Reporters can also blur anything private before sending.
Can I turn off session replay?
Yes, per project, in its settings.
Can reports go to our issue tracker?
Yes, on Pro and Agency: Jira, Asana, Trello and ClickUp, or anything else through the API and webhooks.
Is it free?
Yes, for one active project, including screen recording and session replay.
More ways agencies use Scopepin
Get bug reports you can reproduce the first time.
Free for one project, with unlimited clients and reviewers.