How to report a bug/ia

Iste directivas explica como scriber un bon reporto de defecto o requesta de functionalitate (un carga) in le traciator de cargas de Wikimedia (vide pro plus information). Cargas ben scribite ha plus probabilitate de esser tractate rapidemente.



Recommendationes rapide

 * Sia precise
 * Sia clar: explica 1) como reproducer le situation, passo a passo, sin lassar spatio al interpretation, 2) comportamento expectate, 3) comportamento actual. In sectiones separate
 * Include solo un problema specific o un requesta de functionalitate specific pro cata carga
 * Include omne ligamines e exemplos relevante



Ante que tu face qualcosa


Pote tu reproducer iste problema?
Tenta reproducer le defecto con un version recente del software, pro vider si illo ha jam essite remediate. Si le defecto existe sur un sito wiki como Wikipedia, tu pote essayar le ultime version del software sur test2.wikipedia.org.



Ha un altere persona ja reportate le problema?
Usa le quadro de recerca del traciator de defectos de Wikimedia pro vider si tu defecto ha ja essite reportate o le functionalitate ja ha essite requestate. Tu pote etiam facer recercas plus avantiate sur le pagina de recerca avantiate.

Si tu es incerte si un defecto ja ha essite reportate, tu deberea reportar le defecto. Es melior haber duplicatos de defectos que haber defectos non reportate.



Es possibile que es un problema de accessorio / script de usator?
Alcun problemas es un consequentia de usar scripts de usator e accessorios que necessita alcun correctiones. Il ha con passos explicante como tu pote identificar tal codice, le qual poterea corriger tu problema de sorta que tu non perde tu tempore reportante lo.



Submitter un nove reporto de defecto o requesta de functionalitate
Si tu ha incontrate un defecto in un version recente e pare que nulle altere persona lo ha reportate, alora:
 * 1) Visita phabricator.wikimedia.org.
 * 2) Tu debera aperir session (o registrar te) si tu non lo ha ja facite (vide “”).
 * 3) Clicca sur le button Marcapaginas in le angulo superior a dextra e selige “Reportar un defecto de software” (o “Reportar un problema de securitate” pro ).
 * 4) Completa al minus le sequente campos:
 * 5) * Titulo: Un breve summario de un sol phrase que explica le problema (non tu solution suggerite).
 * 6) ** Bon:
 * 7) ** Mal:
 * 8) * Description: Detalios complete del problema, forniente tote le information que tu actualmente possede. Si isto es insufficiente, on te demandara information additional e te dara consilio sur como obtener lo. This field should include:
 * 9) ** For bugs:
 * 10) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * Exemplo:
 * 1) *** Actual Results: What the application did after performing the above steps.
 * Exemplo:
 * 1) *** Expected Results: What the application should have done, if there was no bug.
 * Exemplo:
 * 1) ** For feature requests:
 * 2) *** A description of what you would like to achieve, and why. Explain what you hope the feature will solve (the actual underlying problem) along with specific examples; but do not demand a specific solution, as there might be other/better solutions. A user story is an effective way of conveying this.
 * Exemplo:
 * 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: If you know specific users who will be interested in getting notified of this task you can add them here. Otherwise, ignore this field.
 * 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: If you know specific users who will be interested in getting notified of this task you can add them here. Otherwise, ignore this field.

Check if your report is complete, then press the "Create Task" button. Your report will now be in the database. This allows somebody interested in the report to look at it and.

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

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



Como reportar un error de JavaScript

 *  See also: 

A lot of functionality, such as gadgets, user scripts, and some parts of MediaWiki, rely on JavaScript.

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 the problem is in the code of a user script or gadget itself, then Phabricator might not be the place where the problem will get handled. Someone might redirect you to the talk page of the script (if the problematic script is identified).



Reporto de un problema de connexion
If you are having difficulties reaching a Wikimedia website at all (slow internet connection etc.), please follow https://wikitech-static.wikimedia.org/wiki/Reporting_a_connectivity_issue



Reporto de un problema de authentication
If you are having problems logging into your account, please follow.

Notas


Vide etiam

 * How to Report Bugs Effectively by Simon Tatham
 * How to get the developer community to solve your problem, by User:MSchottlender-WMF, July 2017
 * Wikimedia Phabricator
 * Writing a good bug report or feature request
 * How to create a good first Bug Report (outdated)
 * Writing a good bug report or feature request
 * How to create a good first Bug Report (outdated)
 * English Wikipedia: Bug reports and feature requests