How to report a bug/ast

Estes regles xenerales espliquen cómo escribir un bon informe de fallu o solicitú de función nel bugtracker de Wikimedia (ver pa más información). Los informes de fallos efeutivos son los que tienen mas posibilidaes d'iguase.

Recomendaciones rápides pa los informes

 * Se precisu
 * Se claru: esplica cómo reproducir el problema, pasu a pasu, pa que otros puedan reproducir el fallu
 * Inclui namái un problema por informe

¿Puedes reproducir el problema?
Tenta reproducir el fallu usando una versión recién del software, pa ver si se corrixió apocayá. Si'l fallu foi nuna wiki como Wikipedia, puedes tentar de probalo na última versión del software qu'hai en test2.wikipedia.org.

¿Informó daquién más del mesmu problema?
Usa'l cuadru de gueta del sistema de siguimientu de fallos de Wikimedia pa ver si yá s'informó del error. Tamién puedes facer guetes más avanzaes na páxina de gueta avanzada.

Unviar un informe de fallu o solicitú de meyora
Si atopasti un fallu nuna versión recién del software y paez que naide más informó del mesmu, entós:
 * 1) Entra en phabricator.wikimedia.org y fai clic en «Tasks & bugs» na barra llateral.
 * 2) Escueye «Crear xera» na esquina cimera derecha.
 * 3) Pidiráte qu'anicies sesión (o que te rexistres) si inda nun lo fixisti (ver «»).
 * 4) Rellena polo menos los siguientes campos:
 * 5) * Títulu (Title): Una descripción curtia d'una frase qu'esplique'l problema (non la solución que suxeres).
 * 6) ** Correuto:
 * 7) ** Incorreuto:
 * 8) * Axudicáu a: (Assigned to) Inora esti campu. Los desendolcadores van axudicalu a daquién cuando planifiquen el trabayu na xera.
 * 9) * Prioridá: Inora esti campu. Polo xeneral, los desendolcadores van una prioridá cuando planifiquen el trabayu na xera (ver Axustar prioridaes).
 * 10) * Description: Full details of the issue, giving as much detail as possible. This can include:
 * 11) ** For bugs:
 * 12) *** 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) *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.
 * 6) * Select the tags (project(s)) in which you've found 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 could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 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 web browsers, skins, or computer systems you've seen the bug on;
 * 2) ***links or diffs to one or more pages where you encountered the bug; or
 * 3) ***whether the problem appears every time, only occasionally, only on certain pages, or only in specific circumstances.
 * 4) *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.
 * 5) * Select the tags (project(s)) in which you've found 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 could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 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 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 all! Thanks for your help to improve MediaWiki and Wikimedia projects!

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.