How to report a bug/sco

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.

Quick recommendations fer reports

 * Be precise
 * Be clear: explain hou tae reproduce the proablem, step bi step, sae that ithers can reproduce the bug
 * Incluid yinlie the ae proablem per report

Can ye 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.

Haes some ither bodie awreadie reported the issue?
Use the search box of Wikimedia's bugtracker to see if your bug has already been reported. You can also perform more advanced searches on the advanced search page.

Reportin ae new bug or featur request
Gif ye'v faced ae bug in ae recynt version n nae ither bodie appears tae'v reported it, than:
 * 1) Go to phabricator.wikimedia.org and click "Maniphest" in the side bar.
 * 2) Choose "Create task" in the upper corner.
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 4) Fil oot at least the follaein fields:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** Guid:
 * 7) ** Bad:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * CC: You should ignore this field: If you know specific users who will be interested in getting notified of this task you can add them here.
 * 10) * Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see "").
 * 11) * Select the project(s) in which you've found the bug:
 * 12) **Projects are how developers find tasks to work on. To identify the right project(s), use the search function (in the top right) to find its description.
 * 13) **This could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 14) * Security: Set this to "Security or Sensitive bug" if many users could be harmed by the security problem that you are reporting. Your report will be kept hidden from the public until it is resolved.
 * 15) * Descreeption: Ful details o the issue, giein aes muckle detail aes possible. This can incluid:
 * 16) ** For bugs:
 * 17) *** Steps tae Reproduce: Makit-smaaest, easie-tae-follae steps that will trigger the descreebed proablem. Incluid onie byordinair setup steps.
 * Example:
 * 1) *** Actual Ootcomes: Whit the appleecation did efter performin the abuin steps.
 * Example:
 * 1) ***Expected Ootcomes: Whit the appleecation shid hae dun, gif thaur wis nae 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 provide onie ither information that micht be uissfu ava, like:
 * 2) ***the wab brousers, skins, or computer systems that ye'v seen the bug oan;
 * 3) ***links or diffs til yin or mair pages whaur ye encountered the bug; or
 * 4) ***whither the proablem kiths ilka time, yinlie occasionlie, yinlie oan certain pages, or yinlie in speceefeec circumstances.
 * 5) *To attach a log file or (but make sure that no confidential data is included or shown), click the Upload File button (a cloud with an arrow) in the tool bar of the Description field.
 * 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 provide onie ither information that micht be uissfu ava, like:
 * 2) ***the wab brousers, skins, or computer systems that ye'v seen the bug oan;
 * 3) ***links or diffs til yin or mair pages whaur ye encountered the bug; or
 * 4) ***whither the proablem kiths ilka time, yinlie occasionlie, yinlie oan certain pages, or yinlie in speceefeec circumstances.
 * 5) *To attach a log file or (but make sure that no confidential data is included or shown), click the Upload File button (a cloud with an arrow) in the tool bar of the Description field.
 * 1) *To attach a log file or (but make sure that no confidential data is included or shown), click the Upload File button (a cloud with an arrow) in the tool bar of the Description field.

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

That's it! Thanks fer yer heelp tae impruiv MediaWiki n Wikimedia waurks!

Reporting a JavaScript bug
When you encounter a bug that may be related to JavaScript, do your best to identify error messages and copy them into the bug report.

It's especially important to provide all the information you have, because even the system administrators will have zero access to any error log. If you are unsure whether a feature you are using is based on JavaScript, try disabling JavaScript.

It's always helpful to include a screenshot with your report. It's often the easiest way to identify which feature you're talking about, and can often provide information which can help narrow down the error. Take care to hide any information you don't want to share, like other open browsers tabs or minimised chat windows.

See ava

 * How to Report Bugs Effectively by Simon Tatham
 * Wikipædia: Bug reports n featur requests
 * Phabricator etiquette
 * Bug management/Bug report life cycle
 * Writing a good bug report or feature request
 * How to create a good first Bug Report (outdated)