Bug #91578 | MySQL Workbench Directs One to a Web Page Rather than Actually Reporting the Bug | ||
---|---|---|---|
Submitted: | 9 Jul 2018 16:06 | Modified: | 30 Jul 2018 16:11 |
Reporter: | Jonathan Shaltz | Email Updates: | |
Status: | Won't fix | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 6.3.10 | OS: | Windows |
Assigned to: | CPU Architecture: | x86 | |
Tags: | bug-reporting, workbench |
[9 Jul 2018 16:06]
Jonathan Shaltz
[10 Jul 2018 5:13]
MySQL Verification Team
Hello Jonathan, Thank you for the reasonable feature request! Thanks, Umesh
[30 Jul 2018 16:11]
Mike Lischke
Posted by developer: From a bug fixing point of view this is not a very welcome approach. To fix an issue you not only need the current status of the app, but exact steps to reproduce the crash. Only a manual report can achieve that, even in 2018. Let's face it: those automatic bug reports help nothing to solve. They are mere statistic than actual bug reports. A robot counts how many people are affected (by trying to guess what belongs together), counts system libs and installed apps a user has and never gives any feedback. This is all but customer friendly. This is not what MySQL understands as real user support.