How to report a bug/ko

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.

보고 시 권장 사항

 * 정확하게 쓰세요.
 * 분명하게, 어떻게 문제를 해결할 수 있는지 단계별로 정리해서 다른 사람들이 버그를 해결할 수 있도록 쓰세요.
 * 버그 하나당 문제는 하나씩.

버그를 해결할 수 있나요?
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. You can also perform more advanced searches on the advanced search page.

새 버그를 보고하거나 기능을 요청하기
만약 최신 버전에서 버그를 발견했고 아무도 보고한 것 같지 않을 때는,
 * 1) Go to phabricator.wikimedia.org and click "Maniphest" in the side bar.
 * 2) Choose "Create task" in the upper corner.
 * 3) 로그인하지 않았다면 로그인하거나 등록할 것을 요청받을 것입니다. (""를 보세요.)
 * 4) 적어도 이 칸은 무조건 채워야 합니다:
 * 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) * 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) * 설명: 최대한 자세히 오류에 대해 설명하세요. 예시는 다음과 같습니다.
 * 11) ** For bugs:
 * 12) *** Steps to Reproduce: Minimized, easy-to-follow steps that will trigger the described problem. Include any special setup steps.
 * 예시:
 * 1) *** 실제 결과: 이 단계들을 따랐을 때 프로그램이 수행하는 것.
 * 예시:
 * 1) ***기대되는 결과: 프로그램에 오류가 없을 때 일어나야 하는 것.
 * 예시:
 * 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.
 * Example:
 * 1) **다음과 같은 유용한 다른 정보들도 주시기 바랍니다.
 * 2) ***오류가 일어난 웹 브라우저, 스킨 또는 컴퓨터 시스템;
 * 3) ***오류를 발견한 문서의 링크; 또는
 * 4) ***문제가 항상 일어나는지, 가끔, 혹은 특정 페이지나 단계를 밟아야 일어나는지.
 * 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) ***오류가 일어난 웹 브라우저, 스킨 또는 컴퓨터 시스템;
 * 2) ***오류를 발견한 문서의 링크; 또는
 * 3) ***문제가 항상 일어나는지, 가끔, 혹은 특정 페이지나 단계를 밟아야 일어나는지.
 * 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.

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

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.

같이 보기

 * 오류를 효과적으로 신고하는 법 (Simon Tatham)
 * Wikipedia: Bug reports and feature requests
 * 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)