Introduction

BugCapture is a browser extension that turns a bug into a filed, QA-ready ticket in one click — without leaving the page where it broke.

Two ways to capture, both attach the same technical context automatically:

• Screenshot. Full page or a cropped region, with an annotator on top — pen, highlighter, shapes, arrows, text, numbered step pins, and blur for anything sensitive.
• Screen recording. A tab or a region (never your whole desktop), with a floating control bar that can pause mid-take or blur an element without stopping the recording.

Every capture — screenshot or video — comes with the same evidence attached automatically: console errors and warnings, network requests, environment (browser, OS, viewport), and, for a video, the console/network trace synced to the moment on the timeline.

What makes a report QA-ready, not just a picture

• Structured fields — Severity, Priority and Environment are set on the report itself, not buried in a description someone has to parse.
• Duplicate detection — a report against a URL and error signature that's already been filed shows "Seen 4×" instead of creating a fifth copy.
• Auto-generated steps to reproduce — recorded clicks and page changes become a numbered list, not a video someone has to rewatch.
• Redaction that travels with the report — blur a card number or an element once, and it stays blurred everywhere that capture is shown.

Where a report goes

A report can be shared as a link, copied as markdown, or filed straight into a tracker — Jira, GitHub, Linear, ClickUp or Notion — or posted to Slack. Filing is free on every plan; nothing about connecting a tracker is gated.

Where to start

• Install the extension — Chrome, Edge or Firefox.
• File your first report — capture, annotate, and send it somewhere.
• Connect your tracker — so "somewhere" is the tool your team already uses.