Re: UI changes in reporting of exceptions

Marian Mirilovic wrote:
> Petr,
> 
> Petr Blaha wrote:
>>> - component/subcomponent
>> We have the list of all component/subcomonent from IZ in server. The 
>> module downloads these info and save this in user dir and update combo 
>> boxes.
> 
> Ok, what if the user will download a new module ? Some modules are hard 
> to map to the source code, how do you want to do that ?

We decided to remove c/s from dialog.


> 
>> simplified reporting exceptions for external users. Of course, this 
>> will require some effort in QE where the reports must be mapped for IZ 
>> issues manually. We are working on some tools that could simplify this 
>> step.
> 
> Thanks for info, let's answer another set of my questions :
> 
> - Do you need user's account ?
> If yes we'll probably miss a lot off reports, if not we'll miss an 
> important information-how often could user get into this troubles.
> 
> - User reported problem, so what would be the feedback to him/her ?

   User will get e-mail about IZ issue.

> 
> - What informations you plan to send to DB ?
> I expect exception-stacktrace, IDE info(version/build), JDK info, OS 
> info, what else ? 

  Only these info we paln to send to server. Do we need the list of all 
installed server?

What about UI gestures ? HW ? Installed modules ?
> Addon Packs ? Do you want to send message.log file ? Installed servers ? 
> Installed DBs ?
> 
> - You said "some tools that could simplify this step" so what are you 
> going to simplify ? The way user reports the exception, 


   This one:

or the way
> somebody will work with data and map them into IZ ?
> 
> - How do you want express the fact that exception was reported by 
> certain number of users ? On different platforms, JDKs, in different 
> situations ?
> 
>>> If we already have answers for these questions, we could much better 
>>> fit the dialog into the appropriate UI ;)
> 
> 
> *Marian
>