Closed Bug 554374 Opened 10 years ago Closed 8 years ago

top crashers by signature needs design <3

Categories

(Socorro :: Webapp, task)

x86
macOS
task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ozten, Assigned: espressive)

References

Details

Attachments

(2 files)

As we put more and more data into top crashers, it's becoming unwieldy.

We need to rethink this report, especially once we've pulled correlation and other related pieces of data into hbase/hadoop and they are more performant that our current system.
Depends on: 554373
Assignee: nobody → chowse
Just a few ideas on how we can show more data on the Top Crashers page:

* Make each row taller, so it can contain more data. This means fewer rows visible at a time, and more difficulty identifying the most relevant data. A little visual design can address the latter. The former is a matter of finding the right balance for our developers.

* Hide certain elements and expose them on clicks or hovers (like we do with charts and bugzilla IDs currently). The key thing is knowing what data users typically scan for (i.e. should always be visible in the table) vs. what they should drill-down for.

* Consider a split-pane approach: display a condensed table, and when the user selects a row, expose more data in a separate panel on the same page. This has the same benefits/downsides as the last point, but could expose more data on the same page, possibly saving a visit to the signature page. This also gives a more room to add extra data in the future.


Just a few ideas for the data we currently have:

* For the ranking and % columns, place the trend/difference label below rather than beside it, to recover valuable horizontal space.

* Consider hiding or limiting the breakdown of crashes by OS. Showing these counts 4 times eats up a lot of space. Do devs typically use all 4 numbers, or just the total, or the total + one OS? If either of the latter is the typical case, a lot of space could be recovered and a lot of clutter removed.

* Correlation reports are useful, but require a lot of space. Consider showing them progressively: display only the most highly correlated modules by default, showing the 5-10 most common (or just those that meet a certain threshold) on a click or hover, and show them in their entirety in a pop-up or a separate pages. Several tricks can be used to make the text of the correlation reports smaller without sacrificing readability (see bug 543605 comment 10 for examples).
Assignee: chowse → nobody
Assignee: nobody → sneethling
[:kairo@mozilla.com] Can you have a look at this as well as the design and let me know if you are happy or what changes you would want to make before I get stuck in.
For one thing, I'm not even sure if I understand everything of comment #1, for the other, I'm not sure it this is the right thing to focus workforce on right now when we have such a long list of other priorities on our Q4 list and we are AFAIK considering to rewrite the whole code for topcrashers anyhow in an upcoming release.
Attached image Second prototype 1
First prototype, specifically the idea of having that 'tabs' on the side for those that are trending up or down. This can also be extended for other states with different 'icons'
For one thing, I don't like the changers being made that obvious as the changer/trend data isn't as good as to be that much prioritized in display. It also looks to me like this display loses the process type icons and graph on-hover icon which is not a good idea.
As I said, I'm not even sure it's a good idea to work on the display of this report at all right now.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #5)
> As I said, I'm not even sure it's a good idea to work on the display of this
> report at all right now.

It's on your Q4 goals list, which is why I asked Schalk to take a look.  Should we drop it off that list?
(In reply to Laura Thomson :laura from comment #6)
> (In reply to Robert Kaiser (:kairo@mozilla.com) from comment #5)
> > As I said, I'm not even sure it's a good idea to work on the display of this
> > report at all right now.
> 
> It's on your Q4 goals list, which is why I asked Schalk to take a look. 
> Should we drop it off that list?

It is? Interesting, I'll talk to Marcia about that, she brought it up to be there. I'm somewhat unsure what we really want out of it.
Whiteboard: Q42011wanted
[:kairo@mozilla.com] This is a very prelimanary prototype, those elements (the on hovers etc.) will not be removed.
I think maybe the reason it made it on there was the Correlation reports aspect - it is difficult to manipulate that part of the data on the top crashers page.

But I agree with KaiRo that while the display of the report can be improved, I am not sure that should be in the bucket of Q4 priorities when we have a lot of other priorities. So I am fine with moving this out of the Q4 bucket.
OK, thanks marcia. The correlation stuff is improve gradually over a few stages, bug 650904 being the first and worked on very soon, other steps will follow, we'll see at what stage we'll be able to improve what we are showing on the topcrasher page.

Given those comments, I'm moving this off the Q4 list for now - sorry Schalk for the back and forth on this.
Whiteboard: Q42011wanted
Component: Socorro → General
Product: Webtools → Socorro
Component: General → Webapp
Schalk has done a bunch of work here.  From here we'll open more specific bugs and close this tracker.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.