How to report a bug/sd

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.

رپورٽن لاءِ تيار شفارشون

 * مختصر ڳالهہ ڪريو.
 * چٽي ڳالهہ ڪريو: مسئلي کي ڪيئن ظاهر جڪي، اهو وکوار طريقي سان سمجھايو تہ جيئن ٻيا ان مسئلي کي ڏسي سگھن.
 * هڪ رپورٽ ۾ صرف هڪڙو ئي مسئلو بيان ڪريو.

ڇا توهان اهو ڳالهوڙو پيدا ڪري ڏيکاري سگھو ٿا؟
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.

ڇا اڳ ۾ ڪنهن ٻي ان ڳالهوڙي جي رپورٽ جمع ڪرائي آهي؟
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.

هڪ نئين جيت يا فيچر درخواست جي رپورٽ ڪرڻ
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 "Maniphest" in the side bar.
 * 2) پنهنجي ڪمپيوٽر جي مٿين حصي ۾"Create task" کي چونڊيو.
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 4) گهٽ ۾ گهٽ هيٺيون جڳهون ڀريو:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** ڀلو:
 * 7) ** خراب:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * CC: 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.
 * 10) * Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see Setting priorities).
 * 11) * "رٿائون" چونڊيو. جن ۾ توهان منگھڻ (بگ) لڌو آهي:
 * 12) **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.
 * 13) **This could be for example the project for the wiki software itself, or  for configuration changes on a Wikimedia site (see "").
 * 14) * Security: Set this to "Security or Sensitive bug" if many users could be harmed by the security problem that you are reporting. Your report will be kept hidden from the public until it is resolved.
 * 15) * تشريح: ڳالهوڙي جا گھڻي ۾ گھڻا ۽ مڪمل تفصيل. ان ۾ هيٺيان اسم شامل ٿي سگھن ٿا:
 * 16) ** منگھڻن لاءِ:
 * 17) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * مثال:
 * 1) *** "اصل نتيجا:" مٿين تي عمل ڪرڻ کان پوءِ ايپليڪيشن ڇا ڪيو؟
 * مثال:
 * 1) ***"متوقہ نتيجا:" ايپليڪيشن ۾ ڪو بہ منگھڻ (بگ) نہ هجڻ جي صورت ۾:
 * مثال:
 * 1) ** فيچر درخوستن لاءِ:
 * 2) *** A description of what you would like to achieve, and why. A user story is an effective way of conveying this.
 * مثال:
 * 1) **مهرباني ڪري ٻي بہ ڪا معلومات فراهم ڪندا، جيڪا ڪارائتي ثابت ٿي سگھي، جهڙوڪ:
 * 2) ***ڪو بہ ويب جھانگھُو، چَمَ، يا ڳڻپيوڪر سرشتو، جنهن ۾ توهان کي منگھڻ (بگ) ڏسجو هجي؛
 * 3) ***links or diffs to one or more pages where you encountered the bug; or
 * 4) ***مسئلو هر وقت رهي ٿو، يا ڪڏهن ڪڏهن ٿو ظاهر ٿي يا ڪن مخصوص صفحن تي يا ڪنهن خاص صورتحال ۾ ظاهر ٿو ٿي.
 * 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.
 * 1) *** A description of what you would like to achieve, and why. A user story is an effective way of conveying this.
 * مثال:
 * 1) **مهرباني ڪري ٻي بہ ڪا معلومات فراهم ڪندا، جيڪا ڪارائتي ثابت ٿي سگھي، جهڙوڪ:
 * 2) ***ڪو بہ ويب جھانگھُو، چَمَ، يا ڳڻپيوڪر سرشتو، جنهن ۾ توهان کي منگھڻ (بگ) ڏسجو هجي؛
 * 3) ***links or diffs to one or more pages where you encountered the bug; or
 * 4) ***مسئلو هر وقت رهي ٿو، يا ڪڏهن ڪڏهن ٿو ظاهر ٿي يا ڪن مخصوص صفحن تي يا ڪنهن خاص صورتحال ۾ ظاهر ٿو ٿي.
 * 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.
 * 1) *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.

"Create Task" دٻائڻ کان اڳ ۾ پڪ ڪريو تہ رپورٽ مڪمل آهي. توهان جي رپورٽ هاڻي اعدادخاني جو حصو بڻجي ويندي، ۽ جلد ئي ڪو ان تي نظر ڊوڙائيندو.

ڪم پُورو! ذريعات‌وڪي ۽ وڪيذريعات رٿائن کي سڌارڻ ۾ مدد لاءِ مهرباني.

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.

پڻ ڏسندا

 * منگھڻ تي اثرائتي رپورٽ ڪيئن تيار ڪجي by سِيمون تاٿم
 * Wikipedia: Bug reports and feature requests
 * Phabricator etiquette
 * Bug management/Bug report life cycle
 * هڪ سٺي جيت رپورٽ ۽ فيچر دخواست لکڻ
 * هڪ سٺي اوائلي منگھڻ رپورٽ ڪيئن تيار ڪجي (مدي خارج)