Developer tools

BetterBugs automatically attaches technical information and data with every bug report you create

Debugging can be difficult without the related technical details of the issue. QA engineers have to worry no more about sending the logs from dev tools separately while reporting the issues to the developers.

BetterBugs automatically attaches key information like console logs, network requests and logs, and system information to the generated bug report.

Overview of all the details attached to every bug report

General information

Detail name	Value(s)
Workspace name	My Workspace (default)
Project name	My Project (default)
Options to share the report with the integrated tools	Jira, Linear, Slack, ClickUp, Asana, GitHub, MS Teams, Trello, Azure Boards
Share	Invite members or share using the report link
Visual proof	Screenshot, Screen recording, Rewind session video
Bug details	Bug title, Manually added or AI-generated description of the issue
Tags	Custom (upto 10 tags)
Priority	Urgent, High, Medium, Low
Status	Open, In Progress, Closed
Upload files	Add upto 5 files | Supported formats: Doc, Excel, PDF, Txt, Image, and Video
Comments/Activities	Custom/System generated

Technical details for developers

Detail name (from the devtools tabs)	Value(s)
Info	Timestamp (Timezone when captured, Your timezone, UTC timezone), URL, Network Speed, Device, Browser Mode, Charging Status, Available Battery, Browser, Window Size, Screenshot Dimensions, Extension Version, App Version, Bug Reporter, IP Address, Country, Timezone, User Agent
Console	Info, Warning, Log, Error, Network Error
Network	Fetch/XHR, JS, CSS, WS, Media, Font, Doc, Manifest, Method, Status
Back-end	Event logs from Sentry (after Sentry integration)
Steps	Page navigation, Network errors, User activities
Metadata	Custom data as "Title and Value" or key: value pairs added by the reporter
Application	Cookies, Local Storage, Session Storage
AI-Debugger	AI-powered root cause analysis, test cases, and possible solutions