How to report a bug/da

These guidelines explain how to write a good bug report or feature request in Wikimedia's bugtracker (see for more information). Effective bug reports are the most likely to be fixed.

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

Har en anden allerede rapporteret emnet?
Use the search box of Wikimedia's bugtracker to see if your bug has already been reported. You can also perform more advanced searches on the advanced search page.

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 and click "Maniphest" in the side bar.
 * 2) Choose "Create task" in the upper corner.
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 4) Udfyld i det mindste følgende felter:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 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) * CC: 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.
 * 10) * Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see "").
 * 11) * Select the project(s) in which you've found the bug:
 * 12) **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.
 * 13) **This could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 14) * Security: Set this to "Security or Sensitive bug" if many users could be harmed by the security problem that you are reporting. Your report will be kept hidden from the public until it is resolved.
 * 15) * Description: Beskriv alle detaljer om emnet, ved at give så mange oplysninger som muligt. Det kan inkludere:
 * 16) ** For bugs:
 * 17) *** 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. A user story is an effective way of conveying this.
 * Example:
 * 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) *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.
 * Example:
 * 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) *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.

Check if your report is complete, then press the "Create Task" button. Your report will now be in the database and somebody will hopefully take a look at it soon.

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

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.

Se også

 * How to Report Bugs Effectively by Simon Tatham
 * 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)