How to report a bug/da

Disse retningslinjer beskriver hvordan en god fejlrapport eller funktions-foresprørgsel skrives i Wikimedia's fejlfinder (se for mere information). Effektive fejlrapporter har størst chance for at blive rettet.

Kort anbefaling til rapporter

 * Be precise
 * Be clear: explain how to reproduce the problem, step by step, so others can reproduce the bug
 * Include only one problem per report

Kan du genskabe emnet?
Prøv at genskabe din fejl ved brug af en ny version af softwaren, for at se om problemet allerede er rettet. Hvis fejlen er på en wiki-hjemmeside som Wikipedia, kan du prøve at teste den seneste software version på [//test2.wikipedia.org test2.wikipedia.org].

Har en anden allerede rapporteret emnet?
Brug søgefunktionen på bugzilla.wikimedia.org for at se om fejlen allerede er rapporteret. Du kan også udføre mere avancerede søgninger på søgesiden.

Rapportér en ny fejl eller funktions-forespørgsel
If you have faced a bug in a recent version and no one else appears to have reported it, then:
 * 1) Go to bugzilla.wikimedia.org.
 * 2) Choose "Enter a new bug".
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 4) Select the product in which you've found the bug:
 * This could be for example for the wiki software itself, or  for configuration changes of the Wikimedia wiki sites.
 * 1) Fill out at least the following fields:
 * 2) * Component: The part of the software the bug happens in. On the right you can see descriptions for each component. If none seems appropriate, use.
 * 3) * Severity: If you request a new feature, please set the severity to.
 * 4) * Summary: A short one-sentence summary that explains the problem (not your suggested solution).
 * 5) ** Godt:
 * 6) ** Dårligt:
 * 7) * Description: Full details of the issue, giving as much detail as possible. This can include:
 * 8) ** 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) **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) *Attachment: You may attach a log file or (but make sure that no confidential data is included or shown).
 * 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) *Attachment: You may attach a log file or (but make sure that no confidential data is included or shown).
 * 1) *Attachment: You may attach a log file or (but make sure that no confidential data is included or shown).

Tjek om din rapport er færdig, og tryk derefter på "Submit bug"-knappen. Din fejlrapport vil nu være i databasen, og nogen vil forhåbentlig tage et kig på den snart.

Det var det hele! Tak for din hjælp til at forbedre MediaWiki og Wikimedia-projekter!

Se også

 * How to Report Bugs Effectively by Simon Tatham
 * The BugZilla song