Fill in what happened, the steps to reproduce and what you expected. Detect your browser and OS in one click, check the quality score, then copy a report formatted for GitHub, GitLab, Jira or plain email.
Runs entirely in your browser. Nothing is uploaded to any server.
Developers can reproduce the issue first time instead of asking questions.
Severity and priority make it easy to sort the backlog.
Environment detection captures details reporters often forget.
The most important part is the steps to reproduce. Start from a known state (for example "logged in as an admin"), keep each step to one action and include the exact data you used. If the bug is intermittent, say how often it happens.
Expected and actual results should be concrete: "Order total shows $54.00" versus "Order total shows $0.00", not "it doesn't work".
What is broken and where, in under 80 characters.
Minimal, numbered and reproducible.
Screenshots, video, console logs or HAR files.
A specific title, minimal numbered steps that reliably reproduce the problem, the expected and actual result, the environment, and evidence such as screenshots or logs.
Severity is the technical impact (a crash is critical). Priority is how soon it should be fixed, which also depends on business impact and how many users are affected.
Your browser and version, operating system, screen and window size, device pixel ratio and language, read locally from the browser. Nothing is sent anywhere.
Markdown for GitHub, GitLab, Linear and most chat tools; Jira markup for Jira Server or Data Center text fields; plain text for email.
Points are given for a specific title, at least two steps, distinct expected and actual results, environment details, frequency and evidence.
More free tools from My Panda Toolbox.