|
|
#1 |
|
Administrator
Join Date: Oct 2008
Posts: 1,329
|
We appreciate your feedback and assistance in finding and squashing all those pesky bugs. In order to help us best, please follow these simple guidelines when reporting an issue:
Do: * Clear title - A good title is a must, as the developer should be able to grasp the essence of the bug report from the title alone. Having a clear title will help get the bug assigned to the correct developer. * One bug per report - Please report one bug in a single report, no more, no less. If you put in too many bugs, some of the them may be overlooked. * Steps to reproduce the problem - This is important. If the bug happens every time you perform a certain series of steps, then the developers will have a much easier time of finding the cause. * Pictures - A picture is worth a thousand words! If you are able to take a screenshot of the problem, include it. Dont's: * Don't write generic titles - Don't write titles like "Help!", "What happen?". These kinds of reports are very hard to understand, and will probably be ignored. So please provide a clear, concise title to your reports. * Don't be rude - Bugs can be frustrating, but the bug report isn't the place to vent that frustration. Remember, the developer is just as frustrated by the bug as you are. |
| Thread Tools | |
| Display Modes | |
|
|