How to report a bug/id

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.

Quick recommendations for reports

 * Be precise
 * Be clear: explain how to reproduce the problem, step by step, so others can reproduce the bug
 * Include only one problem per report

Dapatkah Anda membuat ulang laporan?
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.

Apakah orang lain telah melaporkan masalahnya?
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.

Melaporkan kesalahan / kerusakan atau permintaan fitur
Jika Anda melihat sebuah kesalahan / kerusakan pada versi ini dan belum ada satupun yang melaporkannya, maka:
 * 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) Isilah isian berikut ini:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** Baik:
 * 7) ** Buruk:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see Setting priorities).
 * 10) * Deskripsi: Rincian lengkap masalah, jelaskan selengkap-lengkapnya. Salah satunya:
 * 11) ** For bugs:
 * 12) *** Langkah Untuk Pelaporan Ulang: Singkat, mudah dimengerti dan menjelaskan inti masalahnya. Termasuk semua langkah-langkahnya.
 * Contoh:
 * 1) *** Hasil Akhir: Apa yang dihasilkan program setelah melakukan semua langkah-langkah di atas.
 * Contoh:
 * 1) ***Hasil yang Diharapkan: Hasil apakah yang seharusnya diterima, jika tidak ada kesalahan / kerusakan.
 * Contoh:
 * 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.
 * Contoh:
 * 1) **Harap sertakan informasi berguna lainnya, seperti:
 * 2) ***kesalahan / kerusakan program penjelajah web, tampilan, atau sistem komputer yang anda temukan;
 * 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.
 * 6) * Select the tags (project(s)) in which you've found the bug:
 * 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) **This could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 9) * 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.
 * 1) ***kesalahan / kerusakan program penjelajah web, tampilan, atau sistem komputer yang anda temukan;
 * 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) *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.
 * 5) * Select the tags (project(s)) in which you've found the bug:
 * 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) **This could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 8) * 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.

Selesai! Terima kasih atas bantuan Anda untuk membuat MediaWiki dan Wikimedia project lebih baik!

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.

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.

Lihat juga

 * Bagaimana Cara untuk Melaporakan Kesalahan / Kerusakan Secara Tepat oleh Simon Tatham
 * The BugZilla song
 * Wikipedia: Laporan kesalahan / kerusakan dan permintaan fitur
 * 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)