How to report a bug/sr

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.

Брзе препоруке

 * Будите прецизни
 * Будите јасни: опишите како је дошло до проблема, корак по корак, тако да остали могу репродуковати баг, или га разумети.
 * Укључите само један проблем по задатку
 * Укључите неке релевантне линкове и примере

Can you reproduce the issue?
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, or the feature requested. You can also perform more advanced searches on the advanced search page.

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.

Have you tried fixing the issue yourself?
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) Идите на phabricator.wikimedia.org и кликните на "Tasks & bugs" у бочној траци.
 * 2) Одаберите "Create task" у горњем десном углу.
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 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: Требало би да игноришете ово поље: програмери ће поставити надређеног када буду планирали да раде на задатку.
 * 9) * Description: Сви детаљи проблема, дајући много детаља колико је то могуће. Може садржати:
 * 10) ** За багове:
 * 11) *** Steps to Reproduce: Корак-по-корак како долази до проблема.
 * Пример:
 * 1) *** Actual Results: Шта је апликација урадила након извршења горе наведених корака.
 * Пример:
 * 1) ***Expected Results: Шта би апликација требало да уради.
 * Пример:
 * 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) **Такође наведите и друге информације које могу бити корисне, као што су:
 * 2) ***веб браузери, скинови, или компјутерски системи на којима сте приметили баг;
 * 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) ***веб браузери, скинови, или компјутерски системи на којима сте приметили баг;
 * 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!

Пријављивање Јаваскрипт бага

 * 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.

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).

Пријављивање проблема са везом
If you are having difficulties reaching a Wikimedia website at all (slow internet connection etc.), please follow Reporting a connectivity issue.

Пријављивање проблема са пријављивањем
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
 * 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)
 * English Wikipedia: Bug reports and feature requests