Free tool

Bug report generator

Fill in what happened. Your browser, OS and viewport are added for you, and the result copies as Markdown that Jira, GitHub, Linear or a coding agent can take as is.

Your report, in Markdown

# Untitled bug

Runs in your browser. What you see or type here is not sent anywhere or stored.

Why this structure

A developer fixing a bug needs to do three things: see it happen, know what should have happened, and match your setup. Steps to reproduce cover the first, expected and actual cover the second, and the environment block covers the third. Reports that miss one of them come back with a question, which is usually a day lost.

Writing steps someone else can follow

Start from a page anyone can open, write one action per line, and use the words on the screen (“Tap Checkout”, not “try to pay”). Stop at the step where it goes wrong. If it only happens sometimes, say how often. There is a longer guide, with a template for agents, in how to write a bug report an AI coding agent can fix.

When typing it out is the slow way

For a visual problem on a website, pointing is faster than describing. A Layerdock review link lets the reporter click the element; the screenshot, page, browser and viewport are recorded with the comment, and the pin can be sent on to Jira, Linear, GitHub and other tools.

Skip the copy and paste

With Layerdock, a reviewer clicks the element on the live site and types a comment. The screenshot, page, browser, OS and viewport are attached to the pin automatically, so nobody looks anything up. Try it on your own site, no account needed.

Ready when you are

Make the next
website review easier.

Give your team and clients one clear place to see the issue, capture the context, and share the fix.

Explore the tools

FAQs

Frequently asked questions

About this tool and the numbers it shows.

What should a good bug report include?

A one-line summary, the page address, the steps to reproduce it, what you expected, what happened instead, and the environment: browser, operating system and viewport size. A screenshot helps.

Can I paste the result into Jira, GitHub or Linear?

Yes. The output is Markdown, which GitHub and Linear render directly. In Jira it pastes as plain text that stays easy to read.

Can I give this report to an AI coding agent?

Yes. Agents such as Claude Code and Cursor work well from this structure: numbered steps, expected and actual result, and the environment. Paste it in with the file or page it concerns.

Is what I type saved anywhere?

No. The report is built in your browser as you type. It is not sent to a server or saved, so copy it before you close the tab.