Writing/Logging Bugs....Must read for QA people

Writing is easy, but writing clearly is hard. When it comes to write bug explanations... well, writing seems to get even harder, as far as the IT professional is concerned. In my life as a developer (especially while working at Graycell Technologies) I have seen a lot of bug reports that are either incomplete or missing critical reproducible steps, or have no explanation of why the results are wrong. Juts Imagine (my dear testers) if you were a developer and you got this kind of bug report, won’t you feel frustrated? The best you could do is to mark the case as not reproducible and assigned it back to the tester. The tester, would, in turn would, insisted that the bug was there and, well, there went a football-kicking session. Congratulations, you've wasted a few non-productive minutes on just trying to get message across. All these wasted minutes would add up, resulting in a loss in productivity. And at last it is always a developer’s ass to be kicked