Bug reports that bring the evidence with them

Four ways to report a bug

Pick the report type that matches the problem. Each one is an issue your team can assign, discuss and track.

• Point: a problem at a position on the page. Drag to mark a rectangular area instead.
• Element: a problem with a specific button, field or other element, selected on the page.
• Console: an error or message, reported straight from the console evidence.
• Network: a failed or unexpected request, reported with its request context.

What a report can include

Depending on what was captured and which capabilities are enabled, a report can include a screenshot, the recorded activity around it, console logs, network requests, element context and source attribution.

Claron shows what was actually captured. It does not promise every log from the whole session, so reporters still add what happened, what should happen and the steps that led there.

On a preview or on your live site

Connect a repository and Claron builds a hosted preview your team reviews in the browser. For a site you already host, report right on the live pages with the Claron browser extension, using approved capture permissions.

Add the Claron SDK to your build and every report points straight back to the source element.

Public reports for clients, internal notes for the team

Clients and guests see the public reports in their review, including reports made by other people. Internal annotations and comments stay with project owners, developers and testers.

From report to fix

Reports move through Open, In Review, Resolved, Reopened and Won't Fix. Send one to Linear, Jira, Trello and more when your team is ready. Reports with saved reproduction context offer Claron It!, which walks you back through the captured steps to the problem.