Bug Description

Bug Buddy will ask you to provide a summary and description of the bug you are reporting. If at all possible, please make the report in English. Most developers speak English, although not necessarily as their native language. Writing your report in English will ensure that all developers can understand the problem, which makes it more likely that the problem will be fixed.

The Description text area allows you to describe the problem fully. Bug Buddy automatically inserts a template into the description with the following headers:

Description of Problem

Include a short paragraph providing a brief description of the problem you are reporting.

Steps to reproduce the problem

Include an itemized list of the steps to take to reproduce the problem. Developers cannot fix a problem if they do not know how to reproduce it.

Actual results

Include a short description of what the application actually does when you execute the above steps.

Expected results

Include a short description of what you expect the application to do when you execute the above steps.

How often does this happen?

If the problem does not occur every time you execute the above steps, say how often it occurs. If you can think of any conditions that might have contributed to the problem occurring, let the developers know.

Additional information

If you have any additional information about the problem, please include that information here. For instance, if the programs gives any error messages, you should include that information.

You do not have to fill in all the fields, or follow the template exactly. However, the above information is what is generally useful to developers in most bug reports.

If you have any suggestions on what caused the problem or how to fix it, you can include that. If not, don't worry. Just explain what happened. If a developer needs more information, they may email you back asking for it.