Bug Lens v2.0

Enterprise bug capture and reporting — record, annotate, and submit bugs in seconds.

Capture Bugs. Create Better Defects. Share Faster. Turn your browser testing sessions into clear, actionable defect reports — without manually collecting screenshots, logs, environment details, and reproduction steps. This extension captures your testing flow and brings everything needed for a defect report into one place. 🚀 What it does While you test, the extension can capture: User flows and interactions Steps to Reproduce Screenshots Console logs Failed network requests Application data Browser and device details Instead of manually collecting evidence after finding an issue, the information is available when you start preparing your defect. 🤖 Optional AI-Assisted Defect Writing If you configure your own supported AI API key, the extension can use the captured context to help generate a clear: Defect title Defect description AI is completely optional. You always remain in control of the final report. You can review and edit: Title Description Steps to Reproduce Actual Result Expected Result If the AI-generated content isn't what you want, simply change it before creating or sharing the defect. 🖍️ Screenshot Annotation Make defects easier to understand by annotating captured screenshots. Highlight the exact area where the problem occurred so developers and other team members can quickly identify what needs attention. 🔗 Jira Integration Configure your Jira API details to create defects directly from the extension. Prepare the defect, review the captured evidence, make any necessary edits, and send it to Jira without rebuilding the report manually. 🔔 Slack Notifications Optionally configure Slack integration to notify your team when a defect is created or needs attention. This helps keep defect reporting and team communication connected to the same workflow. 🔒 Privacy First Your testing data belongs to you. Captured information is stored locally using Chrome storage. The extension does not send captured testing data to an external application server. Data is only transmitted to third-party services when you explicitly configure and use integrations such as AI, Jira, or Slack. In those cases, only the information required for the requested integration is sent to that service. ⚡ One Testing Flow Test → Capture → Review → Annotate → Create Defect → Notify No more manually copying console errors. No more rebuilding reproduction steps from memory. No more switching between multiple tools just to prepare a useful defect report. 👥 Built for QA Engineers Test Engineers Developers SDETs Product Teams Support Teams Anyone who reports and investigates web application issues ✨ Key Features at a Glance Flow Capture — Record the actions that led to an issue. Automatic Steps — Draft reproducible steps from the captured flow. Technical Evidence — Collect console logs, failed network requests, application information, and environment details. AI Assistance — Optionally generate clearer defect titles and descriptions using your configured AI key. Fully Editable Reports — Review and modify every important defect field before submission. Screenshot Annotation — Highlight the exact problem area visually. Jira Integration — Create defects directly when Jira is configured. Slack Integration — Notify your team when Slack is configured. Local Storage — Captured data stays in Chrome storage instead of being uploaded to an extension-owned server. Spend less time documenting bugs and more time finding them.