Option to send crash report with or without files containing potential proprietary information

[GoogleCodeExporter]

This is an enhancement request for the ability to mark files attached to the 
report as potentially containing proprietary information(CR_AF_PROPRIETARY). 
Then the crash sender dialog would differentiate the files as proprietary and 
non-proprietary and the user would be able to control which files get sent 
using checkboxes. A tree divided into two parts, proprietary and non 
proprietary would show in the crash sender dialog instead of a flat listbox. 
Some of the files we would like the user to send could contain proprietary 
information which they may want to withhold at the time of sending the report. 
By default the proprietary files would be unchecked. An install option could 
control whether proprietary files are checked for sending by default.

Original issue reported on code.google.com by ABrussZ...@gmail.com on 14 Sep 2012 at 1:59

[GoogleCodeExporter]

I suppose most of user will never set check to those proprietary file 
checkboxes... Not sure if it is a useful feature for most of CrashRpt users. I 
would prefer not to overcomplicate dialogs or menus for users, because most of 
them have no idea about error report content and just click the "Send report" 
or "Close the program" button.

Original comment by zexspect...@gmail.com on 15 Sep 2012 at 4:16

• Changed state: Reviewed
• Added labels: Type-Enhancement, Component-UI
• Removed labels: Type-Defect

[GoogleCodeExporter]

Most users have no idea the first time they see the dialog. Over time though 
especially during alphas and betas, they learn the nuances of the crash sending 
mechanism. The users in our case communicate fairly closely with us. The crash 
reports they send are an integral part of our development process. 

And why then is there an option to delete files that's hidden behind a context 
menu?

This addition could be completely disabled by default and enabled with a flag. 
Our users are scientists and engineers who learn quickly. I think they can 
appreciate the importance of sending proprietary data.

With a more flexible and powerful crash sending process, users will naturally 
like to use it more when the time arrives. 

Thanks for your consideration.

Original comment by ABrussZ...@gmail.com on 18 Sep 2012 at 9:04

[GoogleCodeExporter]

Hmm... why not to just provide the Privacy Policy link? Usually, its difficult 
to differentiate between private and non-private data, so I suppose your 
requested feature would confuse user... 

The feature you mentioned (delete files from context menu) is mostly intended 
for QA (see issue 123). If the feature you request is intended for QA, than 
pivacy is not a problem for QA, I suppose.

Original comment by zexspect...@gmail.com on 19 Sep 2012 at 4:18

[GoogleCodeExporter]

I decided not to implement this feature, as it may confuse user IMHO.

Original comment by zexspect...@gmail.com on 9 Oct 2012 at 2:37

• Changed state: WontFix