How to report a bug/mr

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 worked on quickly.

अहवालासाठीच्या त्वरीत शिफारसी

 * नेमके रहा
 * स्पष्ट रहा:समस्येचे पुरुत्पादन कसे करु शकता त्यास पायरी पायरीने समजवा, जेणेकरुन इतर लोकं त्या गणकदोषास पुनरुत्पादन करुन समजू शकतील.
 * एका अहवालात एकाच समस्येचा अंतर्भाव करा
 * Be clear: explain 1) how to reproduce the situation, step by step, without leaving any room for interpretation, 2) expected behavior, 3) actual behavior. In separate sections
 * Include only one problem per task
 * Include any relevant links and examples

काय आपण त्या बाबीचे पुनरुत्पादन करु शकता?
हे बघण्यास कि तो पूर्वीच ठिकठाक केल्या गेला आहे, संचेतनाची नविनतम आवृत्ती वापरुन, त्या गणकदोषास पुनरुत्पादनाचा प्रयत्न करा. जर तो गणकदोष जर एखाद्या विकिपीडियासारख्या विकि संकेतस्थळावर असेल तर आपण संचेतनाची अद्ययावत आवृत्तीची test2.wikipedia.org वर चाचणी घेऊ शकता.

काय इतर कोणी या बाबीचा अहवाल पूर्वीच दिला आहे?
विकिमिडियाची गणकदोष मागोवा शोधपेटी वापरुन हे बघा कि हा गणकदोष पूर्वीच नोंदविल्या गेला आहे. आपण प्रगत शोध पानावर अधिक प्रगत शोध घेऊ शकता.

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.

Is it maybe a gadget / user script issue?
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) You will have to log in (or register) if you have not already done so (see "").
 * 3) Click the Bookmark button in the upper right corner and choose "Create Task" (or "Report Security issues" to ).
 * 4) Fill out at least the following fields:
 * 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) * Description: Full details of the issue, giving all the information you currently have. If that is insufficient you will be asked for additional information along with guidance on how to obtain it. This field should include:
 * 10) ** For bugs:
 * 11) *** 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) ** For feature requests:
 * 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) ** Please also provide any other information that might be useful, such as:
 * 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).

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

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 https://wikitech-static.wikimedia.org/wiki/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.