How to report a bug/nap

These guidelines explain how to write a good bug report or feature request in Wikimedia's bugtracker (see for more information). Effective bug reports are the most likely to be fixed.

Try the new guided form to file bugs!



Quick recommendations for reports

 * Be precise
 * Be clear: explain how to reproduce the problem, step by step, so others can reproduce the bug
 * Include only one problem per report

Can you reproduce the issue?
Try to reproduce your bug using a recent version of the software, to see whether it has already been fixed. If the bug is on a wiki site like Wikipedia you could try testing the latest software version on [//test2.wikipedia.org test2.wikipedia.org].

Has someone else already reported the issue?
Use the search box on bugzilla.wikimedia.org to see if your bug has already been reported. You can also perform more advanced searches on the search page.

Reporting a new bug or feature request
If you have faced a bug in a recent version and no one else appears to have reported it, then:
 * 1) Go to bugzilla.wikimedia.org.
 * 2) Choose "Enter a new bug".
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 4) Select the product in which you've found the bug:
 * This could be for example for the wiki software itself, or  for configuration changes of the Wikimedia wiki sites.
 * 1) Fill out at least the following fields:
 * 2) * Component: The part of the software the bug happens in. On the right you can see descriptions for each component. If none seems appropriate, use.
 * 3) * Severity: If you request a new feature, please set the severity to.
 * 4) * Summary: A short one-sentence summary that explains the problem (not your suggested solution).
 * 5) ** Buon:
 * 6) ** Cattiv:
 * 7) * Description: Full details of the issue, giving as much detail as possible. This can include:
 * 8) ** For bugs:
 * 9) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * Example:
 * 1) *** Actual Results: What the application did after performing the above steps.
 * Esempie:
 * 1) ***Expected Results: What the application should have done, if there was no bug.
 * Esempie:
 * 1) ** For feature requests:
 * 2) *** A description of what you would like to achieve, and why. A user story is an effective way of conveying this.
 * Example:
 * 1) **Please also provide any other information that might be useful, such as:
 * 2) ***the web browsers, skins, or computer systems you've seen the bug on;
 * 3) ***links or diffs to one or more pages where you encountered the bug; or
 * 4) ***whether the problem appears every time, only occasionally, only on certain pages, or only in specific circumstances.
 * 5) *Attachment: You may attach a log file or (but make sure that no confidential data is included or shown).
 * 1) *** A description of what you would like to achieve, and why. A user story is an effective way of conveying this.
 * Example:
 * 1) **Please also provide any other information that might be useful, such as:
 * 2) ***the web browsers, skins, or computer systems you've seen the bug on;
 * 3) ***links or diffs to one or more pages where you encountered the bug; or
 * 4) ***whether the problem appears every time, only occasionally, only on certain pages, or only in specific circumstances.
 * 5) *Attachment: You may attach a log file or (but make sure that no confidential data is included or shown).
 * 1) *Attachment: You may attach a log file or (but make sure that no confidential data is included or shown).

Check if your report is complete, then press the "Submit bug" button. Your bug report will now be in the database and somebody will hopefully take a look at it soon.

That's all! Thanks for your help to improve MediaWiki and Wikimedia projects!

Può v'rè pur

 * How to Report Bugs Effectively by Simon Tatham
 * The BugZilla song
 * Wikipedia: Bug reports and feature requests