Home › Guides › What should I include in a bug report?

What should I include in a bug report?

By the Nextbug editorial team · independent guide
October 13, 2026
What should I include in a bug report?

The non-negotiable five

Title: Describe the actual problem, not "it's broken." Use `[Component] Specific issue` format.

Steps to reproduce: Exactly what you did before the bug appeared. "Click login, enter credentials, click submit" beats "login doesn't work."

Expected result: What should have happened.

Actual result: What actually happened instead.

Environment: Operating system, browser version, or app version where you found it.

Nice to have

Screenshots or screen recordings show the problem instantly. Error messages and logs let developers debug faster. Your device specs matter if it's hardware-specific.

What not to include

Don't guess at the cause. Don't add feature requests. Don't include unrelated problems in one report.

Format for speed

Use the same template every time. Copy-pasting is fine. Developers scan these in seconds—make the structure predictable.

Reader reviews

Write a review

← All guides