How to report a bug/lt

These guidelines explain how to write a good bug report or feature request in Wikimedia's bugtracker (see for more information). Effective bug reports are the most likely to be fixed.

Sparčios rekomendacijos pranešimams

 * Būk tikslus
 * Būk suprantamas: paaiškink kaip atstatyti problemą, žingsnį po žingsnio, kad kiti galėtų atstatyti klaidą
 * Įtrauk tik vieną problemą už pranešimą

Ar galiu atstatyti svarstomą problemą?
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.

Ar kiti jau pranešė svarstomą problemą?
Naudokitės paieškos laukeliu per bugzilla.wikimedia.org, kad pamatytumėte, ar jūsų klaida jau buvo pranešta. Jūs galite taip pat atlikti daugiau sudėtingesnių paieškų paieškos puslapyje.

Naujos klaidos pranešimas arba ypatybės prašymas
Jeigu susidūrėte su klaida naujoje versijoje ir niekas apie ją dar nepranešę, tai:
 * 1) Eikite į phabricator.wikimedia.org ir spauskite Maniphest" šoninėje juostoje.
 * 2) Pasirinkite Sukurti užduotį viršutiniame kampe.
 * 3) You will be asked to log in (or register) if you have not already done so (see "").
 * 4) Užpildykite bent vieną iš šių laukų:
 * 5) * Title: A short one-sentence summary that explains the problem (not your suggested solution).
 * 6) ** Geras:
 * 7) ** Blogas:
 * 8) * Assigned to: You should ignore this field: Developers will set an assignee when they plan to work on the task.
 * 9) * Priority: You should ignore this field: In general, the priority is set by developers who plan to work on the task (see Setting priorities).
 * 10) * Description: Full details of the issue, giving as much detail as possible. This can include:
 * 11) ** Klaidoms:
 * 12) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * Pavyzdys:
 * 1) *** Actual Results: What the application did after performing the above steps.
 * Pavyzdys:
 * 1) ***Expected Results: What the application should have done, if there was no bug.
 * Pavyzdys:
 * 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.
 * Pavyzdys:
 * 1) **Prašome taip pat pateikti kitą informaciją, kuri gali būti naudinga:
 * 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: 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) * 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: 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.

Štai ir viskas! Ačiū už jūsų pagalbą, kad pagerinote MediaWiki ir Wikimedia projektus!

Reporting a JavaScript bug
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.

Taip pat skaitykite

 * How to Report Bugs Effectively by Simon Tatham
 * Wikipedia: Bug reports and feature requests
 * Phabricator etiquette
 * Bug management/Bug report life cycle
 * Writing a good bug report or feature request
 * Kaip sukurti pirmą gerą Bug Report (outdated)