Wéi ee Feeler (Bug) mellen

From MediaWiki.org
Jump to: navigation, search
This page is a translated version of the page How to report a bug and the translation is 40% complete.

Outdated translations are marked like this.
Other languages:
aragonés • ‎العربية • ‎asturianu • ‎تۆرکجه • ‎беларуская (тарашкевіца)‎ • ‎български • ‎català • ‎čeština • ‎Cymraeg • ‎dansk • ‎Deutsch • ‎Ελληνικά • ‎English • ‎Esperanto • ‎español • ‎euskara • ‎فارسی • ‎suomi • ‎français • ‎galego • ‎Hawaiʻi • ‎עברית • ‎हिन्दी • ‎hrvatski • ‎Kreyòl ayisyen • ‎magyar • ‎Հայերեն • ‎Bahasa Indonesia • ‎Interlingue • ‎italiano • ‎日本語 • ‎ქართული • ‎Taqbaylit • ‎ಕನ್ನಡ • ‎한국어 • ‎Ripoarisch • ‎Lëtzebuergesch • ‎lietuvių • ‎मराठी • ‎Bahasa Melayu • ‎Napulitano • ‎norsk bokmål • ‎Nederlands • ‎occitan • ‎ଓଡ଼ିଆ • ‎ਪੰਜਾਬੀ • ‎polski • ‎پښتو • ‎português • ‎português do Brasil • ‎română • ‎русский • ‎sicilianu • ‎Scots • ‎سنڌي • ‎සිංහල • ‎slovenčina • ‎shqip • ‎svenska • ‎தமிழ் • ‎తెలుగు • ‎ไทย • ‎Türkçe • ‎татарча/tatarça • ‎ئۇيغۇرچە • ‎українська • ‎ייִדיש • ‎粵語 • ‎中文
shortcut: BUGREPORT

Dës Richtlinnen erkläre wéi een e Feeler (Bug) oder eng Ufro no enger Funktioun gutt am Wikimedia Bugtracker beschreift (kuckt PhabricatorPhabricator fir méi Informatiounen). Gutt geschriwwe Rapporten iwwer Feeler hu méi Chance fir verbessert ze ginn.

Feelermeldunge mussen op Englesch gemaach ginn. Wann Dir keen Englesch schreiwe kënnt, da probéiert eng automatiséiert Iwwersetzung wéi Google Translate ze benotzen.

E puer Recommandatioune fir Feelermeldungen

  • Sidd präzis
  • Sidd kloer: erklärt wéi de Feeler reproduzéiert ka ginn, Schrëtt fir Schrëtt, esou datt Anerer de Feeler reproduzéiere kënnen
  • Setzt just ee Feeler an eng Feelermeldung

Ier Dir eppes maacht

Ier Dir eppes maacht

Kënnt Dir de Feeler reproduzéieren?

Versicht Äre Feeler mat enger rezenter Versioun vun der Software ze reproduzéiere fir z'iwwerpréiwen ob e scho verbessert ass. Wann Dir de Feeler op engem Wiki-Site wéi Wikipedia fonnt hutt da kéint Dir probéieren fir e mat där aktuellster Software-Versioun vun test2.wikipedia.org ze testen.

Huet schonn een Aneren de Problem signaliséiert?

Benotzt d'Sichkëscht op dem Wikimedia 'Bugtracker' fir ze kucken op Äre Feeler scho gemellt gouf. Dir kënnt och méi detailléiert sichen op der Erweiderter-Sich-Säit.

En neie Feeler mellen oder eng nei Fonctioun ufroen

If you have faced a bug in a recent version and no one else appears to have reported it, then:

  1. Gitt op phabricator.wikimedia.org a klickt op "Maniphest" an der säitlecher Läischt.
  2. Wielt "Aufgab uleeën" am ieweschten Eck eraus.
  3. You will be asked to log in (or register) if you have not already done so (see "Creating your accountPhabricator/Help#Creating_your_account").
  4. Fëllt mindestens dës Felder aus:
    • Title: A short one-sentence summary that explains the problem (not your suggested solution).
      • Gutt: "Selecting gender is not functional."
      • Schlecht: "Software crashes."
    • Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
    • Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see Setting priorities).
    • "Beschreiwung": Ausféierlech, méiglechst komplett Informatiounen iwwer de Problem. Dat kann dëst sinn:
      • Fir Feeler (bugs):
        • Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
          Beispill:
          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.
        • Actual Results: What the application did after performing the above steps.
          Beispill:
          "There is no female gender in front of my user name."
        • Expected Results: What the application should have done, if there was no bug.
          Beispill:
          "My gender is shown in front of my user name."
      • For feature requests:
        • A description of what you would like to achieve, and why. A user story is an effective way of conveying this.
          Beispill:
          "As a new editor, I would like to be acknowledged for my contribution to the project, so that I feel welcomed and valued"
      • Please also provide any other information that might be useful, such as:
        • 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.
    • To attach a log file or screenshotHelp:Screenshots (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.
    • Sicht d(e) "Projet(en)" eraus an deem Dir de Feeler fonnt hutt:
      • 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.
      • This could be for example the MediaWiki-General-or-Unknown project for the wiki software itself, or Wikimedia-Site-Requests for configuration changes on a Wikimedia site (see "Selecting projectsPhabricator/Help#Selecting_projects").
    • Subscribers: 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.

Kuckt ob Äre Rapport komplett ass, da klickt op de Knäppchen "Create task". Är Feelermeldung ass dann an der Datebank gespäichert an hoffentlech hëlt da geschwënn ee sech dem Feeler un.

Dat ass alles! Merci fir Är Hëllef fir MediaWiki an d'Wikimedia Projeten ze verbesseren!

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.

Kuckt och