How to report a bug/id

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

Quick recommendations

 * 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

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?
Gunakan kotak pencarian di bugtracker Wikimedia untuk melihat apakah kesalahan/kerusakan telah dilaporkan sebelumnya. Anda juga dapat melakukan pencarian lebih lanjut di halaman pencarian lebih lanjut.

Melaporkan kesalahan / kerusakan atau permintaan fitur
Jika Anda melihat sebuah kesalahan / kerusakan pada versi ini dan belum ada satupun yang melaporkannya, maka:
 * 1) Buka phabricator.wikimedia.org dan klik "Maniphest" di side bar.
 * 2) Pilih "Create task" di pojok kanan atas.
 * 3) Anda akan diminta untuk log in (atau mendaftar), jika Anda belum mendaftar. (lihat "").
 * 4) Isilah isian berikut ini:
 * 5) * Title: Sebuah kalimat pendek yang menjelaskan permasalahan (bukan sebuah pemecahannya).
 * 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) ** Untuk bug:
 * 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) * Lampiran: Anda boleh menyertakan log / catatan atau (pastikan tidak menyertakan atau menampilkan data-data yang rahasia).
 * 6) * Pilih tag (proyek) yang ditemukan kesalahan/kerusakan:
 * 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) * Lampiran: Anda boleh menyertakan log / catatan atau (pastikan tidak menyertakan atau menampilkan data-data yang rahasia).
 * 5) * Pilih tag (proyek) yang ditemukan kesalahan/kerusakan:
 * 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.

Periksa kembali laporan anda, lalu tekan tombol "Create Task". Laporan kesalahan/kerusakan yang anda buat akan ada dalam database kami dan akan diperiksa sesegera mungkin.

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

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.

Lihat juga

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