Bug #63388 Bug reporter does not automagically fillout the majority of this form
Submitted: 22 Nov 2011 17:58 Modified: 13 Jul 2013 23:48
Reporter: asdf asdf Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[22 Nov 2011 17:58] asdf asdf
Description:
Well, I don't know what more to say.

While I care about the error I'm getting, I'm gonna be copy pasting, no... wait... I CAN'T copy the error from the MySQL Workbench Unexpected Error dialog.

All I can copy is this:
--------------
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team
-------------

Not very useful. Eh?

How to repeat:
1) Get an error
2) Click [Report Bug] button

Suggested fix:
1) Make all of the text in error dialogs selectable so you can copy past.  This goes double for THE ACTUAL ERROR TEXT".

2) BONUS POINTS - Why not just have the error dialog pass along the majority of the info to bugs.mysql.com?  I mean really, these are the internets and this is the future.  Let's get with it.  :-)
[23 Nov 2011 9:15] Valeriy Kravchuk
As we speak about MySQL Workbench here, I do agree that, when suggesting to report a bug, it should fill most of the fields in the bug report from the information it already has internally. This is a valid and reasonable feature request.

In the meantime, when you get error dialog box, please, right click somewhere in it and use Copy stack trace to clipboard context menu item. Paste stack trace to the bug report you create. This is the most useful part of information about the error in any case.
[13 Jul 2013 23:48] Alfredo Kojima
The reporting form already auto-fills everything it can, it can't know the context of where an error occurs.