How to report a bug/lb

Dës Richtlinnen erkläre wéi een e Feeler (Bug) oder eng Ufro no enger Funktioun gutt beschreift mat Hëllef vum Wikimedia Bugtracker (kuckt fir méi Informatiounen). Gutt geschriwwen Aufgaben hu méi Chance fir datt séier drop geschafft gëtt.

E puer Recommandatiounen

 * Sidd genee
 * Be clear: explain 1) how to reproduce the situation, step by step, without leaving any room for interpretation, 2) expected behavior, 3) actual behavior. In separate sections
 * Include only one specific bug or one specific feature request per task
 * Include any relevant links and examples

Kënnt Dir de Feeler reproduzéieren?
Versicht Äre Feeler mat enger rezenter Versioun vun der Software ze reproduzéiere fir z'iwwerpréiwen ob e scho verbessert ass. Wann Dir de Feeler op engem Wiki-Site wéi Wikipedia fonnt hutt da kéint Dir probéieren fir e mat där aktuellster Software-Versioun vun test2.wikipedia.org ze testen.

Huet schonn een Aneren de Problem signaliséiert?
Benotzt d'Sichkëscht op dem Wikimedia 'Bugtracker' fir ze kucken op Äre Feeler scho gemellt gouf. Dir kënnt och méi detailléiert sichen op der Erweiderter-Sich-Säit.

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.

Ass et vläicht e Problem mat engem Gadget oder engem Script vun engem Benotzer?
Some problems are a consequence of using user scripts and gadgets which need some fixes. There is with steps how you can identify such code, which could fix your issue so that you do not waste your time reporting it.

En neie Feeler mellen oder eng nei Fonctioun ufroen
If you have faced a bug in a recent version and no one else appears to have reported it, then:
 * 1) Gitt op phabricator.wikimedia.org.
 * 2) You will have to log in (or register) if you have not already done so (see "").
 * 3) Click the Bookmark button in the upper right corner and choose "Create Task" (or "Report Security issues" to ).
 * 4) Fëllt mindestens dës Felder aus:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** Gutt:
 * 7) ** Schlecht:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * "Beschreiwung": Ausféierlech, méiglechst komplett Informatiounen iwwer de Problem. Dat kann dëst sinn: If that is insufficient you will be asked for additional information along with guidance on how to obtain it. This field should include:
 * 10) ** Fir Feeler (bugs):
 * 11) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * Beispill:
 * 1) *** Actual Results: What the application did after performing the above steps.
 * Beispill:
 * 1) *** Expected Results: What the application should have done, if there was no bug.
 * Beispill:
 * 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.
 * Beispill:
 * 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) * Sicht d(e) Markéierunmgen (Projet(en)) eraus an deem Dir de Feeler fonnt hutt:
 * 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) * Sicht d(e) Markéierunmgen (Projet(en)) eraus an deem Dir de Feeler fonnt hutt:
 * 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.

Kuckt ob Äre Rapport komplett ass, da klickt op de Knäppchen "Create task". Äre Rapport gëtt dann an der Datebank gespäichert. 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).

Dat ass alles! Merci fir Är Hëllef fir MediaWiki an d'Wikimedia Projeten ze verbesseren!

Ee JavaScript-Feller mellen

 *  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).

Reporting a connectivity issue
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

Reporting a login problem
If you are having problems logging into your account, please follow Manual:How to debug/Login problems.

Kuckt och

 * Wéi e Feeler efficace melle kann! vum Simon Tatham (op englesch)
 * How to get the developer community to solve your problem, by User:MSchottlender-WMF, July 2017
 * Wikimedia and  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)
 * English Wikipedia: Bug reports and feature requests