How to report a bug/hr

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!



Brze preporuke za izvješća

 * Budite precizni
 * Budite jasni: objasnite kako reproducirati problem, korak po korak, tako da drugi mogu reproducirati bug
 * Priložite samo jedan problem po izvješću

Možete li reproducirati problem?
Pokušajte reproducirati svoj bug koristći najnoviju verziju softvera, kako bi vidjeli da li je već riješen. Ako je bug na wiki stranicama poput Wikipedije možete pokušati testirati najnoviju verziju softvera na [//test2.wikipedia.org test2.wikipedia.org].

Je li netko već prijavio problem?
Upotrijebite okvir za pretraživanje na bugzilla.wikimedia.org kako bi vidjeli da li je vaš bug već prijavljen. Također možete obaviti više naprednih pretraživanja na stranici za pretraživanje.

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) ** Good:
 * 6) ** Bad:
 * 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.
 * Example:
 * 1) ***Expected Results: What the application should have done, if there was no bug.
 * Example:
 * 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).

Provjerite je li vaše izvješće dovršeno, a zatim pritisnite tipku "Submit bug". Vaša prijava buga sad će biti u bazi i nadamo se da će to netko uskoro pogledati.

To je sve! Hvala za vašu pomoć da se poboljšaju MediaWiki i Wikimedia projekti!

Vidi također

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