http://blogs.msdn.com/b/micahel/archive/2007/01/03/resolvingresolutions.aspxAnu asks: [C]ould you post an entry on when to resolve a bug as "Dupe" or "No repro". I've been following the rule of resolve a bug as dupe if and only if the repro steps of the 2 bugs are the same. If they are the same root cause, it totally dependsen-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/micahel/archive/2007/01/03/resolvingresolutions.aspx#1433404Mon, 08 Jan 2007 12:08:05 GMT91d46819-8472-40ad-a661-2c78acb4018c:1433404Shrini<p>Some related Discussion ....</p> <p><a rel="nofollow" target="_new" href="http://shrinik.blogspot.com/2006/09/bug-or-feature.html">http://shrinik.blogspot.com/2006/09/bug-or-feature.html</a></p> <p>Shrini</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1433404" width="1" height="1">http://blogs.msdn.com/b/micahel/archive/2007/01/03/resolvingresolutions.aspx#1430894Mon, 08 Jan 2007 00:34:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:1430894Bevan McCabe<p>Re the Not Repro section:</p> <p>If your testing team is a bit 'under-resourced', then you can't be a thorough tester. In this scenario you would accept that the bug has been fixed without worrying about exactly when.</p> <p>Time spent worrying about that is put to better use by chasing down other bugs.</p><div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1430894" width="1" height="1">