Bug #88291 Please allow 'Can't repeat' > 'Open' bug db status change
Submitted: 30 Oct 2017 7:43 Modified: 2 Nov 2017 6:18
Reporter: Roel Van de Paar (OCA) Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Websites: bugs.mysql.com Severity:S2 (Serious)
Version: OS:Any
Assigned to: CPU Architecture:Any

[30 Oct 2017 7:43] Roel Van de Paar
Description:
Example;
https://bugs.mysql.com/bug.php?id=88265

Current status: "Can't repeat"

Desired status: "Open"

Other states like "Need feedback" auto-reset to "Open" when feedback is provided.

The change for "Can't repeat" does not need to automatically back to "Open", but it would be handy to be able to set this status as an external bug reporter using the Status field. Currently only "Can't Repeat" and "Closed" is possible.

Otherwise, unless the personally who originally set the "Can't repeat" status is actively monitoring replies to bugs, bugs that have been responded to by the original reporter or others can easily be missed.

How to repeat:
Please also set bug #88265 back to Open.
[30 Oct 2017 12:23] Umesh Shastry
Hello Roel,

Thank you for the feedback.
I'm leaving it for concern people to take a call on this i.e allow 'Can't repeat' > 'Open'. Imho - this was implemented to prevent opening bugs intentionally/unintentionally from reporters or users comments, preventing spammers from changing bug status etc. In any case, notification is sent to verifier who in turn can take an action whether to open or respond with justification etc.

Coming to Bug #88265, we(me and Miguel) confirmed that even though 8.0.3 debug build is affected(commented with details) but it is no longer reproducible with latest source which is 8.0.4. We, at verification team most of the time first try to confirm with the reported version, then with GA(if reported version is not GA) and finally with latest daily builds(latest source, or binaries available internally from daily builds) and this helps save development team time as well.

Tried to find closest one to confirm which internal/external bug fixed reported issue but couldn't locate the same and hence we marked it as 'can't repeat' which is ideal for such situations.

I suggest you to wait for 8.0.4 to out, give it a try at your end and report us back if you are still seeing the issue.

Thank you once again!

Thanks,
Umesh
[2 Nov 2017 6:18] Roel Van de Paar
Thank you Umesh for testing 88265 against 8.0.3 and considering this bugs.mysql.com feature request.