Here's the recommendation from Joel on Software:
It's pretty easy to remember the rule for a good bug report. Every good bug report needs exactly three things.
- Steps to reproduce
- What you expected to see
- What you saw instead
[/size]
Source: Painless Bug Tracking -
http://www.joelonsoftware.com/articles/fog0000000029.html