#180: ABRT2 gui review
---------------------------------+------------------------------------------
Reporter: jmoskovc | Owner: kirkb
Type: usability assessment | Status: assigned
Priority: major | Component: Interaction Design / Usability
Severity: Moderately Involved | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by kirkb):
Just working through the submission screens and I see that the latest
version of ABRT in Fedora now has the analysis and submission steps as
different.
Could you help me understand a few things?
1 - Does the user pick one and only one analyzer for each crash? Once
they've picked one it looks like they can't pick another? Is this true
even if the analysis fails (i.e. retrace server is busy)?
2 - Why would a user pick one analyzer over another? Do they perform
different types of analysis?
3 - Why should the user do the analysis? What value does it provide to
the user? To the bug report reader?
4 - Is there a good default set of analyzers to include in Fedora? Could
we default to one, then try another, then another if things fail? This
presumes that they all do the same type of analysis.
Thanks for your help in understanding this! You can see my latest screens
(SVGs for now) here:
http://kirkb.fedorapeople.org/ABRT/
--
Ticket URL: <
https://fedorahosted.org/design-team/ticket/180#comment:23>
Design Team <
http://fedoraproject.org/wiki/Design>
Fedora Design Team