A software bug (or just "bug") is an error, flaw, mistake, "undocumented feature", failure, or fault in a computer program that prevents it from behaving as intended (e.g., producing an incorrect result). Most bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few are caused by compilers producing incorrect code.
A program that contains a large number of bugs, and/or bugs that seriously interfere with its functionality, is said to be buggy. Reports detailing bugs in a program are commonly known as bug reports, fault reports, problem reports, trouble reports, change requests, and so forth. More details here: All About Software Bugs
In order to limit the amount of spam tickets we receive and need to clean up, you need to identify yourself by logging in to Assembla, Google or Yahoo.
When documenting the bug, it is absolutely mandatory that as much detail as possible be mentioned. The very first thing anyone will do when trying to fix the bug, will be to reproduce it. If the problem can't be reproduced, there is little chance that it will get solved.
Be sure to write any details that will help the developer reproducing the bug:
Creating a patch
If you happen to know the solution to the bug you have found, we encourage you to post the solution in the ticketOf course, all the details about the bug will still be absolutely necessary. Alternatively, we encourage you to get write access to the ImpressCMS SVN and fix the bug yourself directly in the ImpressCMS SVN repository. To learn more about this, have a look here.