How to report a bug/pt

Estas diretrizes explicam como escrever um relatório de falhas ou um pedido para novas funcionalidades (uma tarefa) no centro de gestão de tarefas Wikimedia (consulte para saber mais). As tarefas com textos bem redigidos irão criar muito mais interesse por parte dos voluntários em colaborar na sua resolução.

Recomendações rápidas para reportações

 * Seja preciso
 * Seja claro: explique como reproduzir o problema, passo a passo, de modo que outras pessoas possam reproduzir o bug
 * Inclua apenas um problema por reportação

Consegue reproduzir o problema?
Tente reproduzir o problema usando uma versão recente do software, para ver se já foi reparado. Se o problema estiver numa wiki como o Wikipédia, poderia testar a última versão do software em test2.wikipedia.org.

Já alguém reportou o problema?
Use a caixa de procura no $mediazilla2 para ver se o erro já foi relatado. Pode também fazer buscas mais avançadas na página de buscas.

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.

Reportar um novo bug ou requisitar uma funcionalidade
Se encontrou um erro numa versão recente, ainda nao relatado, então: Atribuído a: Você pode ignorar este campo: Os desenvolvedores definirão um responsável, quando planejarem trabalhar na tarefa.
 * 1) Go to phabricator.wikimedia.org and click "Tasks & bugs" in the side bar.
 * 2) Choose "Create task" in the upper right corner.
 * 3) Deverá iniciar sessão (ou registar-se) se ainda não o fez(veja "").
 * 4) Preencha, no mínimo, os campos que seguem:
 * 5) * "Titulo:" Uma frase curta que explique o problema (não a sugestão sugerida)
 * 6) ** Bom:
 * 7) ** Ruim:
 * 1) * Description: Full details of the issue, giving as much detail as possible. This can include:
 * 2) ** Para bugs:
 * 3) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * Exemplo:
 * 1) *** Actual Results: What the application did after performing the above steps.
 * Exemplo:
 * 1) ***Expected Results: What the application should have done, if there was no bug.
 * Exemplo:
 * 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.
 * Exemplo:
 * 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) * Selecione o produto onde encontrou o erro
 * 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) ***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) * Selecione o produto onde encontrou o erro
 * 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.

Check if your report is complete, then press the "Create Task" button. Your report will now be in the database and somebody will hopefully take a look at it soon.

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

É tudo! Obrigado por ajudar a melhorar os projetos MediaWiki e Wikimedia!

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.

Ver também

 * How to Report Bugs Effectively por 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)
 * Wikipédia: Reportar bugs e requisitar uma funcionalidade