I've written a lot of bugs (and fixed a few!) in the last 8 years and came up with the following template for bug Descriptions. By putting all of this info in every Description, it will be easy for developers to reproduce & QA to verify fixes.
STEPS: 1. do something 2. do something else 3. confirm that something is true RESULTS: Something is not true. In fact, something else is true. EXPECTED: Something is true. Thanks! -e ---=---===------- Elliot Winard Sr. Software Engineer Laszlo Studios ---=---===-------
