- Make sure you set the case type properly - for a bug, the type should be... well... "Bug".
The 'summary' field in the case report is the first thing Pentaho developers see when reviewing submitted cases, so make that description short but precise. For instance, instead of describing your problem as 'Receiving exception when running a report', you might be a bit more precise: 'BIRT report exception \ [odaconsumer.CannotGetColumnCount\] causes report to fail'. Wiki Markup
- The 'environment' field gives you the opportunity to describe any unique factors in your system environment that could affect the case. For example, what JRE or SDK are you running? What operating system is the application running on? What application server are you using?
- When filling in the 'description' field of the case report, the more detail for a reproduction of the bug you can give us, the better chance we have of finding and fixing said bug. Include details such as what exactly went wrong, the steps you took to reproduce the error, and what you expected to happen.
- Be sure to set YOUR name as the Community Assignee. This will help us communicate with you regarding your case submissions, and give you credit for the work you submit.