How to report a bug/lb

Dës Richtlinnen erkläre wéi een e Feeler (Bug) oder eng Ufro no enger Funktioun gutt am Wikimedia Bugtracker beschreift (kuckt fir méi Informatiounen). Gutt geschriwwe Rapporten iwwer Feeler hu méi Chance fir verbessert ze ginn.

E puer Recommandatioune fir Feelermeldungen

 * Sidd präzis
 * Sidd kloer: erklärt wéi de Feeler reproduzéiert ka ginn, Schrëtt fir Schrëtt, esou datt Anerer de Feeler reproduzéiere kënnen
 * Setzt just ee Feeler an eng Feelermeldung

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.

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: Gitt op phabricator.wikimedia.org a klickt op "Maniphest" an der säitlecher Läischt. Wielt "Aufgab uleeën" am ieweschten Eck eraus. Sicht d(e) "Projet(en)" eraus an deem Dir de Feeler fonnt hutt:
 * 1) You will be asked to log in (or register) if you have not already done so (see "").
 * 2) Fëllt mindestens dës Felder aus:
 * 3) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 4) ** Gutt:
 * 5) ** Schlecht:
 * 6) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 7) * Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see Setting priorities).
 * 8) * "Beschreiwung": Ausféierlech, méiglechst komplett Informatiounen iwwer de Problem. Dat kann dëst sinn:
 * 9) ** Fir Feeler (bugs):
 * 10) *** 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. 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.
 * 1) *** A description of what you would like to achieve, and why. 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.
 * 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.
 * 1) **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.
 * 2) **This could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 3) * 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.

Kuckt ob Äre Rapport komplett ass, da klickt op de Knäppchen "Create task". Är Feelermeldung ass dann an der Datebank gespäichert an hoffentlech hëlt da geschwënn ee sech dem Feeler un.

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

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.

Kuckt och

 * Wéi e Feeler efficace melle kann! vum Simon Tatham (op englesch)
 * Wikipedia: Bug reports and feature 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)