Perceive

Bug Reporting How-To?

Awhile back I stumbled across a document targeted to users that explains what a programmer needs in a bug report to be able to quickly fix a bug, without having to email back and forth a billion times to the user. Does anyone happen to know of such a document? I've googled until my brain is about to explode without any luck.