Bug #49830 once a report is marked as "can't repeat" it cannot be opened
Submitted: 19 Dec 2009 22:15 Modified: 2 May 2012 19:16
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Websites: bugs.mysql.com Severity:S3 (Non-critical)
Version:anyoneanywhere OS:Any
Assigned to: Vlad Safronov CPU Architecture:Any
Tags: qc

[19 Dec 2009 22:15] Peter Laursen 
Description:
With reference to http://bugs.mysql.com/?id=49825 I can state that once a report is marked as "can't repeat" it cannot be opened again. Reporter can only change to "closed".

How to repeat:
... it would be a bad idea to repeat ... :-)

Suggested fix:
Original reporter (at least) should be able to reopen *any* bug report if he is able to provide what additional info is required.
[19 Dec 2009 22:23] Peter Laursen 
YASTC 
(yet another synopsis typo correction .. :-( )
[20 Dec 2009 7:43] Valeriy Kravchuk 
This was done for a reason. We had cases when "bug" reporter kept re-opening bugs without any good reason for weeks. Why not just to add comment? Usually engineer who set bug to "Can't repeat" not only gets any further comments as emails, but also keeps track ofthe state and re-opens the report if needed. In your last example with --install and service creation I think your new report was different enough to keep it and NOT re-open older one.

But OK, this is a feature request to cosnider in any case. Thank you.
[20 Dec 2009 9:42] Peter Laursen 
I can understand that there must be an option to say 'enough is enough'. But I think that should be a seperate flag.

To this "Usually engineer who set bug to "Can't repeat" not only gets
any further comments as emails, but also keeps track of the state and
re-opens the report if needed." I can tell that my experience is that adding comments to a closed bug has no effect in most cases.  I often had reply to such comments. I do not know if comments were read.

But of course it is possible to create a new report.  If current behavior is intentional and provides best workflow for you then you may keep it of course.
[2 May 2012 19:16] Vlad Safronov 
Closing old ticket. Won't fix. Current behavior is intentional.