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

 * Vær præcis
 * Udtryk dig klart: forklar hvordan problemet genskabes skridt for skridt, så andre kan genskabe fejlen
 * Inkludér kun ét problem i hver rapport

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.

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

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.

Rapportér en ny fejl eller funktions-forespørgsel
Hvis du har stået overfor en fejl i en ny version og ingen andre ser ud til at have rapporteret den, så:
 * 1) Go to phabricator.wikimedia.org.
 * 2) Du vil blive bedt om at logge ind (eller registrere) hvis du ikke allerede har gjort det (se "").
 * 3) Click the Bookmark button in the upper right corner and choose "Create Task" (or "Report Security issues" to ).
 * 4) Udfyld i det mindste følgende felter:
 * 5) * Title: En kort enkelt-sætnings beskrivelse, som forklarer problemet (ikke din foreslåede løsning).
 * 6) ** Godt:
 * 7) ** Dårligt:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * Description: Beskriv alle detaljer om emnet, ved at give så mange oplysninger som muligt. Det kan inkludere:
 * 10) ** For bugs:
 * 11) *** Skridt at genskabe: Kortfattet, letfølgelige skridt, som udløser det beskrevne problem. Inkluder alle særlige opsætnings skridt.
 * Eksempel:
 * 1) *** Faktiske resultat: Hvad program-stykket gjorde efter udførelsen af ovenstående trin.
 * Eksempel:
 * 1) *** Forventet resultat: Hvad program-stykket burde have gjort, hvis der ikke var nogen fejl.
 * Example:
 * 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.
 * Eksempel:
 * 1) ** Venligst fremlæg også alle andre oplysninger, som kan være nyttige, såsom:
 * 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: Du kan vedhæfte en logfil eller (men sørg for, at der ikke fortrolige data er inkluderet eller vist).
 * 6) * Vælg produktet, hvor du har fundet fejlen:
 * 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) ** Det kunne for eksempel være for wikisoftwaren selv, eller  for konfigurationsændringer på Wikimedia wiki websites.
 * 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) * Attachment: Du kan vedhæfte en logfil eller (men sørg for, at der ikke fortrolige data er inkluderet eller vist).
 * 5) * Vælg produktet, hvor du har fundet fejlen:
 * 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) ** Det kunne for eksempel være for wikisoftwaren selv, eller  for konfigurationsændringer på Wikimedia wiki websites.
 * 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.

Tjek om din rapport er færdig, og tryk derefter på "Create Task"-knappen. Din fejlrapport vil nu være i databasen, og nogen vil forhåbentlig tage et kig på den snart. 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).

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

Reporting a JavaScript bug

 * See also: Help:Locating broken scripts

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

Se også

 * Hvordan rapportere fejl effektivt, af 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)
 * English Wikipedia: Bug reports and feature requests