About this tool
Not every team uses Jira. This generator produces a tracker-neutral bug report for GitHub issues, Azure DevOps, Linear, Confluence or a plain email, and it records two things that decide how a bug gets handled: how reliably it reproduces and whether it is a regression. "Intermittent, 3 of 10 attempts" tells a developer to look for timing or state problems; "Regression, last good build 2.30.4" lets them diff two builds instead of debugging from scratch. The GitHub format leaves the title out of the body (it has its own field), turns "Key: value" environment lines into a table and lists attachments as a checklist so you remember to drag the files in.
How to use it
- Enter a specific title and a one-line description of who is affected.
- List the steps, the expected and actual results, and the environment as "Key: value" lines.
- Set reproducibility (always, intermittent with a count, or seen once) and whether it worked in an earlier build.
- Choose Markdown, GitHub issue or plain text, then copy or download. Work in progress is saved in this browser.
Bug Report Generator FAQ
How do I report a bug I can only reproduce sometimes?
Choose Intermittent and record how many times it happened out of how many attempts. Add anything that seemed to correlate (first run after login, slow network, a particular account) in the description. A ratio is far more useful than "sometimes".
Why ask for the last good build?
If you know the bug is a regression and the last build where it worked, developers can compare the two builds or bisect the commits in between. That is usually much faster than debugging the current build alone.
Can I attach screenshots here?
No. Files stay with your tracker. List the file names in Attachments so reviewers know what evidence exists, then upload them in GitHub, Jira or wherever the report goes.