Bug Report
From FIFE development wiki
[edit] Filing a BUG Report
To file a bug report please go to our Trac page and click on the New Ticket heading. Please use the following as a guideline on how to fill out a bug report:
[edit] Summary
A brief description of the bug. Try to be as descriptive as possible without going into much details. Good examples of BUG descriptions are:
- Segfault when closing the FIFE
- Widgets are not properly re-sized when loaded from XML
[edit] Reporter
If you hang out in IRC please use your IRC nick here. It will be helpful because we will be able to identify you if we need to ask you any questions regarding the bug.
[edit] Description
This is a detailed report about the bug. Please be as descriptive as possible. The more detail you include the better chance that a developer will be able to reproduce the problem and fix it. Please include the following information:
- FIFE version number (or if you are using SVN please refer to the revision you are using)
- Platform and Operating System you are using. Be sure to include the following:
- Operating systems and versions that you can recreate the bug on
- FIFE dependency version numbers
- How to reproduce the bug. Be clear in how to reproduce the bug.
- Expected result. Include what you think should have happened when you take the steps you described above.
- Actual result. What actually happens when following the steps you described above. Please include any backtraces or debug information you collected.
[edit] Type
Select "defect" (default). If you are requesting a new feature please select "enhancement".
[edit] Priority
When bug should be fixed? Set the priority from LOWEST to HIGHEST. Please use your own judgment here. If this is a major bug which causes the engine to crash for example then set it to HIGHEST.
[edit] Milestone
Leave the default setting
[edit] Component
Select the component that directly relates to the bug. If this is unknown select "engine".
[edit] Version
Leave the default setting for now
[edit] Severity
This describes the impact of the bug.
Types of Severity:
- Blocker: No further testing work can be done.
- Critical: Application crash, Loss of data.
- Major: Major loss of function.
- Minor: Minor loss of function.
- Trivial: Some small enhancements.
