Hvordan fejl rapporteres

Phabricator is for software bug reports, feature requests, and planning work.

• To ask technical questions about Wikimedia projects, see m:Tech
• To ask technical questions about MediaWiki in non-WMF installations, see Project:Support desk

Disse retningslinjer beskriver hvordan en god fejlrapport eller funktions-foresprørgsel skrives i Wikimedia's fejlfinder (se Phabricator for mere information). Effektive fejlrapporter har størst chance for at blive rettet. Fejlrapporter skal skrives på engelsk. Hvis du ikke kan skrive engelsk, så prøv at benytte et maskinoversættelses-værktøj såsom Google Translate.

Kort anbefaling til rapporter

• Vær præcis
• Udtryk dig klart: forklar 1) hvordan problemet genskabes skridt for skridt, uden plads til fortolkning, 2) forventet adfærd, 3) eegentlig adfærd. I separate sektioner
• Indtaster kun én specifik fejl eller en specifik funktion anmodning pr. opgave

• Include any relevant links and examples

Før du gør noget som helst

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.

Is it maybe a gadget / user script issue?

Some problems are a consequence of using user scripts and gadgets which need some fixes.

There is a guide available with steps how you can identify such code, which could fix your issue so that you do not waste your time reporting it.

Is it a caching issue?

Some issues relate to older cached HTML being served alongside newer JavaScript where the two are incompatible. To help determine if this is the cause it is helpful to purge the page, refresh the page and see if the issue persists and include this information in your bug report.

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 "hvorfor? ").
3. Click the Bookmark button in the upper right corner and choose "Report a Software Bug" (or "Report a Security Issue" to report a security problem ).
4. Udfyld i det mindste følgende felter:
   • Title: En kort enkelt-sætnings beskrivelse, som forklarer problemet (ikke din foreslåede løsning).
     • Godt: "Selecting gender is not functional on Special:Preferences"
     • Dårligt: "Software crashes"
   • Beskrivelse: Beskriv alle detaljer om emnet, ved at alle de informationer du har. If that is insufficient you will be asked for additional information along with guidance on how to obtain it. This field should include:
     • For bugs:
       • Skridt at genskabe: Kortfattet, letfølgelige skridt, som udløser det beskrevne problem. Inkluder alle særlige opsætnings skridt.

         Eksempel:

         1. Go to https://en.wikipedia.org with Internet Explorer version 10.0;
         2. Make sure you are logged in;
         3. Select "My Preferences" menu;
         4. Go to "Gender" and select female gender from box list;
         5. Click "Save" button.

       • Faktiske resultat: Hvad program-stykket gjorde efter udførelsen af ovenstående trin.

         Eksempel:

         "There is no female gender in front of my username."

       • Forventet resultat: Hvad program-stykket burde have gjort, hvis der ikke var nogen fejl.

         Example:

         "My gender is shown in front of my username."

     • For feature requests:
       • 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:

         "As a new editor, I would like to be acknowledged for my contribution to the project, so that I feel welcomed and valued"

     • Venligst fremlæg også alle andre oplysninger, som kan være nyttige, såsom:
       • the web browsers, skins, or computer systems you've seen the bug on;
       • links or diffs to one or more pages where you encountered the bug; or
       • whether the problem appears every time, only occasionally, only on certain pages, or only in specific circumstances.
   • For at vedhæfte en logfil eller skærmbillede (men sørg for, at ingen fortrolige data er inkluderet eller vist), skal du klikke på knappen Upload fil (en sky med en pil) i værktøjslinjen i feltet Beskrivelse.
   • Vælg produktet, hvor du har fundet fejlen:
     • 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.
     • Det kunne for eksempel være MediaWiki-General-or-Unknown for wikisoftwaren selv, eller Wikimedia-Site-Requests for konfigurationsændringer på Wikimedia wiki websites.
   • 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 potentially work on it .

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

Se også: 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 https://wikitech-static.wikimedia.org/wiki/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 .

Notes

Se også

• Hvordan rapportere fejl effektivt, af Simon Tatham
• Wikimedia Phabricator
  • Phabricator etiquette
• Bug management/Bug report life cycle
• Writing a good bug report or feature request

• English Wikipedia: Bug reports and feature requests