Ooops I did it again!!

The embarrassing mistakes (that I recall of now) I've made while reporting Defects/Bugs from my Rookie days till now:

Obvious ones:
1>Asked to refer a attachement in report, never attached one to the report.
2>Incorrect Spelling/Grammer.
3>Expecting a developer to understand the context in which I have filed the defect. i.e. not specifying the steps to reproduce.
4>Reporting a defect on incorrect version.
5>Re-opening a defect on a version which is not yet released. (I know, What was I thinking).
6>Refering to wrong table for values which I would not find in them.

Tricky ones:
1>While testing for values in a recently added column in a table forgot to sort query results in desc. order.
That way the entries for older records was ZERO/NULL and I think it's a defect.
2>Mentioned in defect report that I clicked on a buuton,when I actually hit a button using keyboard.


Ofcourse the Idea here is not to show how naive I was in my early years as a tester, but to get to know common mistakes we all make.
Well ofcourse also to gain something out of it!!!

Tell me about yours?

How long before you close a defect

I was testing a pretty tricky defect today. I realised that I had encountered a similar defects 3-4 versions/builds back.
At first I was suprised as too why did it re-earth. Did I not test it enough before closing it?
As I pondered on it, I wondered when is the right time to close a defect.The answer will be very simple -->The moment you think it will not occur again:)
However life is not that simple now is it?

There are many things you wil have to look out for:

1.Severity of the defect.
2.Probability of it's occurance.
3.Confidence in the developer.

However I still not able to figure out when is the best time to close a defect.

1.After couple of regression rounds?
2.Just retesting it over a couple of builds/version?
3.If the unit testing results are very positive?

Any suggestions?