BugJar

About

BugJar lets anyone — developers, QA, clients, project managers — report bugs with full technical context, using a step-by-step reproduction flow.

HOW IT WORKS
1. Open BugJar on the page with the bug
2. Describe the issue, choose category and priority
3. Add reproduction steps — each step captures its own screenshots, console logs, network requests, and DOM elements
4. Click Generate Report — sends to your configured integrations and saves to History

CAPTURE
- Screenshots with annotation editor (pen, arrows, rectangles, text)
- Console logs with timestamps and stack traces for errors
- Network requests (XHR/fetch) with status, duration, and response body for failures
- DOM Inspector — click any element to capture tag, classes, CSS selector, XPath
- Framework detection (Angular, React, Vue, jQuery)
- SPA navigation tracking (pushState/replaceState)
- localStorage/sessionStorage key listing
- Full environment info (OS, browser, resolution, timezone, touch)

INTEGRATIONS
- Azure DevOps: creates Work Items with full HTML body and uploaded screenshot attachments
- GitHub Issues: creates issues with category/priority labels
- Slack: sends formatted thread with structured files (.md reports, screenshots)
- Email: opens mail client with pre-filled report

PER-SITE PROFILES
Route bug reports to different integrations per client/project using URL pattern matching. BugJar auto-selects the right profile based on the current page URL.

PRIVACY & SECURITY
- Zero secrets in source code — all credentials stored locally in chrome.storage
- No data sent anywhere except your configured integrations
- No analytics, no telemetry, no tracking
- Open source: github.com/jgounand/BugJar

BUILT FOR AI
Reports are structured Markdown files optimized for Claude and ChatGPT — paste them directly for instant root cause analysis.

Available in English, French, and Spanish. Dark mode follows your system preference.