How to report a bug/sco

Thir guidelines explain hou tae write ae guid bug report or featur request in Wikimedia's bugtracker (see fer mair information). Effecteeve bug reports ar the maist likelie tae be fixt.

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?
Gie reproduicin yer bug ae shot uisin ae recynt version o the safware, tae see whither it haes awreadie been fixt. Gif the bug is oan ae wiki steid like Wikipædia ye coud gie testin the latest saffware version ae shot oan test2.wikipedia.org.

Haes some ither bodie awreadie reported the issue?
Uise the rake kist oan $mediazilla2 tae see gif yer bug haes awreadie been reported. Ye can dae mair advanced rakes oan the rake page ava.

If you are unsure whether a bug has already been reported, you should report the bug. It is better to have duplicate bugs than it is to have unreported bugs.

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 "Tasks & bugs" in the side bar.
 * 2) Choose "Create task" in the upper right corner.
 * 3) Ye'll be speired tae log in (or register) gif ye'v na awreadie dun sae (see "").
 * 4) Fil oot at least the follaein fields:
 * 5) * Title: Ae short yin-sentence ootline that explains the proablem (na yer 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) * Descreeption: Ful details o the issue, giein aes muckle detail aes possible. This can incluid:
 * 10) ** For bugs:
 * 11) *** 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) * Attachmant: Ye micht attach ae log file or (bit be sair that nae confidential data is incluidit or shawn).
 * 6) * Select the product whaur in ye'v foond the bug:
 * 7) **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.
 * 8) ** This coud be fer example fer the wiki saffware itsel, or  fer confeeguration chynges o the Wikimedia wiki steids.
 * 9) * Subscribers: 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.
 * 1) ***the wab brousers, skins, or computer systems that ye'v seen the bug oan;
 * 2) ***links or diffs til yin or mair pages whaur ye encountered the bug; or
 * 3) ***whither the proablem kiths ilka time, yinlie occasionlie, yinlie oan certain pages, or yinlie in speceefeec circumstances.
 * 4) * Attachmant: Ye micht attach ae log file or (bit be sair that nae confidential data is incluidit or shawn).
 * 5) * Select the product whaur in ye'v foond the bug:
 * 6) **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.
 * 7) ** This coud be fer example fer the wiki saffware itsel, or  fer confeeguration chynges o the Wikimedia wiki steids.
 * 8) * Subscribers: 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.

Check gif yer report is compleate, than press the "Create Task" button. Yer report will nou be in the database n somebodie will hopefulie tak ae luik at it suin.

The priority for the task will be set by developers who plan to work on the task (see Setting priorities).

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

Reporting a JavaScript bug

 * See also: Help:Locating broken scripts

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

 * Hou tae Report Bugs Effecteevelie bi Simon Tatham
 * How to get the developer community to solve your problem, by User:MSchottlender-WMF, July 2017
 * 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)
 * Wikipædia: Bug reports n featur requests