How to report a bug/ksh

Heh kam_mer lässe, wi mer ene johde Fählerbereesch udder Verbäßerongswonsch schriive un en de Fählerdahebangk vun Wikkimehdija ennrejsche deiht. Op dä Sigg vum  jidd_et noch mieh Einzelheite. Johde Fählerbereeschte sorrje för bäßer Schangse, dat sesch ene Fähler och reparrehre löht.

Koote Ämfählonge för Fählerbereeschte

 * Bes jenou!
 * Donn Schrett för Schrett opschrihve, wat De jenou jedonn häs.
 * För jehdes Problehm schriiv ene eije Bereesch!

Kanns De dat norr_en hen krijje?
Try to reproduce your bug using a recent version of the software, to see whether it has already been fixed. If the bug is on a wiki site like Wikipedia, you could try testing the latest software version on test2.wikipedia.org.

Hädd_ene andere dat alld jemälldt?
Use the search box of Wikimedia's bugtracker to see if your bug has already been reported, or the feature requested. You can also perform more advanced searches on the advanced search page.

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.

Have you tried fixing the issue yourself?
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.

Ene Fähler udder ene Verbäßerongswonsch mällde
Wann De en Fähler ene aktoälle Väsjohn fengks, un et sühd esu uß, wi wann dä noch keine andere jemälldt hä, dann:
 * 1) Jangk op   un klek op „Maniphest“ aan de Sigg.
 * 2) Do wehß jefrohch, Desch enzelogge, udder neu aanzemällde, falls De dat noch nit jedonn häs. Loor op „“
 * 3) Click the star in the upper right corner and choose "Create Task" (or "Report Security issues" to ).
 * 4) Föll winneschsdens heh di Vällder uß:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** Johd:
 * 7) ** Schlääsch:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * Description: Full details of the issue, giving as much detail as possible. This should include:
 * 10) ** För Fähler:
 * 11) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * Beijschpell:
 * 1) *** Wat verhaftesch eruß kohm: Wat de Aanwändong dann jedonn hät.
 * Beijschpell:
 * 1) ***Wat De äwahd häs: Wat de Aanwändong sullt jedonn han.
 * Beijschpell:
 * 1) ** Beij Verbäßerongswönsch
 * 2) *** Schrihv op, wat De äreijsch han wells, un woröm. En [$story Jescheesch] es och ene johde Wähsch, dat ze donn. 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.
 * E Beijschpell:
 * 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!

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.

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

Loor och heh

 * Wi mer Fähler johd mälldt vum 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)
 * Wikipedia: Fähler mällde un Verbäßeronge vörschlonn