How to report a bug/nb

Disse veiledningene forklarer hvordan å skrive en god bug rapport eller en forbedrings funksjon i Wikimedia's bugtracker (se for mer informasjon). Effektive bug rapporter er mest sannsynlig for å bli fikset.

Hurtig rekommendasjoner for rapporter

 * Vær nøyaktig
 * Vær klar: Forklar hvordan man kan skape problemet, steg for steg, så andre kan skape det samme problemet
 * Inkluder bare ett problem per rapport

Kan du skape problemet på nytt ?
Prøv å reproduser ditt problem ved å bruke en lingnende verson av programmet, for å se om det har allerede blitt fikset. Vis problemet er på en av wiki sidene som for eksempel Wikipedia kan du prøve å teste det seneste versonen av programmet på test2.wikipedia.org

Har noen andre allerede rapportert problemet?
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.

Rapportere et nytt problem eller en funksjons forespørsel
Vis du har møtt på et problem i en senere verson og ingen andre ser ut til å rapportert det, så :
 * 1) Go to phabricator.wikimedia.org.
 * 2) Du vil bli spurt om å logge inn (eller registrere) vis du ikke allerede har gjort det (Se "").
 * 3) Click the Bookmark button in the upper right corner and choose "Create Task" (or "Report Security issues" to ).
 * 4) Fyll ut ivertfall følgene felt:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** Bra:
 * 7) ** Dårlig:
 * 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 as much detail as possible. This 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.
 * Eksempel:
 * 1) *** Actual Results: What the application did after performing the above steps.
 * Eksempel:
 * 1) ***Expected Results: What the application should have done, if there was no bug.
 * Eksempel:
 * 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.
 * Eksempel:
 * 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) * Velg det produktet hvor du har funnet problemet:
 * 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) ** Dette kan være for eksempel for wiki-programmet i seg selv, eller  for konfigurerings-forandringer på Wikimedia Wiki sider.
 * 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) * Velg det produktet hvor du har funnet problemet:
 * 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) ** Dette kan være for eksempel for wiki-programmet i seg selv, eller  for konfigurerings-forandringer på Wikimedia Wiki sider.
 * 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 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.

Se også

 * 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 (utdatert)
 * English Wikipedia: Bug reports and feature requests