A guide to askingWrite a useful bug report

Report the bug
so someone can reproduce it.

A useful report says what you did, what you expected, and what happened. Include the steps someone needs to see the problem.

About a 2-minute read

A conversation that stalls

Sara

Your website is broken! Please fix it.

The location of the problem and the steps to reach it are missing.

A question someone can answer

Sara

In Firefox, I open Settings, change the language, and click Save. I expect the new language to remain, but refreshing restores the old one. I can reproduce this in a private window too.

The behavior, expectation, and reproduction steps are clear.

Report observations. Label your guesses.

Include the environment, application version, and shortest steps that reproduce the issue. If it only happens sometimes, say so and describe how often you have seen it. Separate what you observed from what you think caused it.

For visual problems, a screenshot helps. For errors or code, include text someone can copy. Add any workaround you have found so the report is useful to users as well as maintainers.

Remove passwords, tokens, session identifiers, and user data from reports and screenshots. Report security vulnerabilities through the project’s designated private channel.

Before you send your question

0 of 4 ready
A starting point for your next question
Keep the conversation goingShare what solved it

Other projects

Other projects for people who like to learn and build.

Sources and inspirationDon’t Ask to AskNo HelloThe XY ProblemMinimal, Reproducible ExampleTheBestLanguage