Bir sorunu nasıl rapor ederim?

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 24% 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

These guidelines explain how to write a good bug report or feature request (a task) in Wikimedia's task tracker (see PhabricatorPhabricator for more information). Well-written tasks are more likely to be worked on.

Sorunlar İngilizce olarak dile getirilmelidir. Eğer İngilizce olarak yazamıyorsanız,Google Translate gibi bir çeviri asistanı kullanabilirsiniz.

Raporlar için hızlı öneriler[edit]

  • Be precise
  • Be clear: explain how to reproduce the problem, step by step, so others can reproduce the bug, or understand the request.
  • Include only one problem per task
  • Include any relevant links and examples

Bir şey yapmadan önce[edit]

Yanlışlığı bir daha yapabilir misin?[edit]

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.

Daha önce birisi bu sorunu rapor etti mi?[edit]

Use the search box of Wikimedia's bugtracker to see if your bug has already been reported, or the feature requested. You can also perform more advanced searches on the advanced search page.

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.

Reporting a new bug or feature request[edit]

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

  1. Go to phabricator.wikimedia.org and click "Tasks & bugs" in the side bar.
  2. Choose "Create task" in the upper right corner.
  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. Fill out at least the following fields:
    • Title: A short one-sentence summary that explains the problem (not your suggested solution).
      • İyi: "Selecting gender is not functional."
      • Kötü: "Software crashes."
    • Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
    • Description: Full details of the issue, giving as much detail as possible. This can include:
      • Hatalar için:
        • Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
          Örnek:
          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.
        • "Gerçek Sonuçlar:" Yukarıdaki adımları uyguladıktan sonra uygulamanın ne yaptığı.
          Örnek:
          "There is no female gender in front of my user name."
        • "Beklenen Sonuçlar: Hata olmadan uygulamanın ne yapması gerektiği.
          Örnek:
          "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.
          Örnek:
          "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.
    • Select the tags (project(s)) in which you've found the bug:
      • 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.

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.

The priority for the task will be set by developers who plan to work on the task (see Setting priorities).

That's all! Thanks for your help to improve MediaWiki and Wikimedia projects!

Reporting a JavaScript bug[edit]

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.

Ayrıca bakınız[edit]