How to report a bug/ar

هذه القواعد تشرح "كيف تَكتُب تقرير مشكلة او طلب ميزة جيد" (واجب) في متابع مهام ويكيميديا (تابع للمزيد من المعلومات). المهام المكتوبة جيداً لها احتمالية انجاز اكبر.

توصيات سريعة

 * كن دقيقاً
 * كن واضحاً: اشرح كيف تعيد انتاج المشكلة، خطوة بخطوة، لكي يُنتِجُها الآخرون، او لفهم الطلب.
 * اضمِن مشكلة واحدة فقط لكل مهمة
 * اضمِن اي رابط او مثال ذو صلة

هل يمكنك اعادة انتاج المشكلة؟
حاول انْ تعيد انتاج مشكلتك باستعمال اصدار حديث من البرنامج، لترى اذا اُصلِحَت، اذا كانت المشكلة في موقع ويكي مثل ويكيبيديا، يمكنك انْ تحاول تجربة احدث اصدار للبرنامج على test2.wikipedia.org.

هل سبق وأن قام أحد بالإبلاغ عن هذه المشكله؟
استعمل صندوق بحث متتبع مشاكل ويكيميديا لترى اِنْ كانت مشكلتك موجودة سابقاً، او طلبت الميزة، يمكنك ايضاً القيام ببحث متقدم في صفحة البحث المتقدم.

اذا لم تكن متأكداً اَنَّ مشكلتك ابلغت سابقاً، ينبغي عليك الابلاغ عن المشكلة. من الافضل ان يكون هناك مشاكل مضاعفة من ان يكون هناك مشاكل غير مبلغة.

هل حاولت حل المشكلة بنفسك؟
Some problems are a consequence of using user scripts and gadgets which need some fixes. There is with steps how you can identify such code, which could fix your issue so that you do not waste your time reporting it.

الإبلاغ عن خلل جديد او طلب خدمة جديدة
اذا واجهت خلل في النسخة الحالية ولا أحد سبق له وأن واجه نفس الخلل، عليك: (انظر "").
 * 1) Go to phabricator.wikimedia.org.
 * 2) سيطلب منك تسجيل الدخول (او فتح حساب جديد)
 * 1) Click the Bookmark button in the upper right corner and choose "Create Task" (or "Report Security issues" to ).
 * 2) إملأ على الأقل الحقول التالية :
 * 3) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 4) ** جيد:
 * 5) ** سيء:
 * 6) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 7) * Description: Full details of the issue, giving as much detail as possible. This should include:
 * 8) ** للأعطال:
 * 9) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * مثال :
 * 1) *** Actual Results: What the application did after performing the above steps.
 * مثال:
 * 1) ***Expected Results: What the application should have done, if there was no bug.
 * مثال:
 * 1) ** لطلبات الميزات:
 * 2) *** A description of what you would like to achieve, and why. Explain what you hope the feature will solve (the actual underlying problem) along with specific examples; but do not demand a specific solution, as there might be other/better solutions. A user story is an effective way of conveying this.
 * مثال:
 * 1) **الرجاء إضافة أية معلومات أخرى قد تكون مفيدة ، مثل :
 * 2) ***the web browsers, skins, or computer systems you've seen the bug on;
 * 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: If you know specific users who will be interested in getting notified of this task you can add them here. Otherwise, ignore this field.
 * 1) ***the web browsers, skins, or computer systems you've seen the bug on;
 * 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: If you know specific users who will be interested in getting notified of this task you can add them here. Otherwise, ignore this field.

Check if your report is complete, then press the "Create Task" button. Your report will now be in the database. This allows somebody interested in the report to look at it and.

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

هذا كل شئ! شكرا على مساعدتك لتطوير مشاريع ميدياويكي و ويكيميديا

Reporting a JavaScript bug

 * See also: Help:Locating broken scripts

A lot of functionality, such as gadgets, user scripts, and some parts of MediaWiki, rely on JavaScript.

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 the problem is in the code of a user script or gadget itself, then Phabricator might not be the place where the problem will get handled. Someone might redirect you to the talk page of the script (if the problematic script is identified).

Reporting a connectivity issue
If you are having difficulties reaching a Wikimedia website at all (slow internet connection etc.), please follow Reporting a connectivity issue.

Reporting a login problem
If you are having problems logging into your account, please follow Manual:How to debug/Login problems.

انظر أيضا

 * How to Report Bugs Effectively by Simon Tatham
 * How to get the developer community to solve your problem, by User:MSchottlender-WMF, July 2017
 * إتيكيت فابريكاتور
 * Bug management/Bug report life cycle
 * Writing a good bug report or feature request
 * How to create a good first Bug Report (مهمل)
 * English Wikipedia: Bug reports and feature requests