828002 - Crash Reports Feature Request: Ability to sort individual reports by plug-in version

Status: RESOLVED FIXED

(Socorro :: Webapp, task, P3)

Description

[Jeromie Clark]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.101 Safari/537.11

Steps to reproduce:

In the course of attempting to fix issues without reproducible steps, we ship blind fixes to our Beta channel.  If the issue persists, we want to pull the individual call stacks specifically for the versions we targeted with the candidate fix.  This is currently very time-consuming, because there's no way to determine what version of our plug-in a particular report corresponds to.  A sortable column for plug-in version or DLL name (at least for Flash Player) would be terribly helpful.

https://crash-stats.mozilla.com/report/list?signature=F1812794833_________________________

(Click Reports, and attempt to find a report for Flash Player 11.6.102.111, for instance.)

Comment 1

[Benjamin Smedberg]

Laura, how much work is this? I'm happy to point Jeromie at the rewritten webapp for this, if it has production data.

Comment 2

[Laura Thomson :laura]

I think the easiest way to do this is actually to add it to advanced search, which already lets you search by plugin name/filename.

Passing over to Adrian for an estimate.

Comment 3

[[DEACTIVATED] Adrian Gaudebert]

This is not doable with search as search shows aggregated signatures and we want here to see individual reports. Doing this in report/list seems possible and not too complicated, but that implies adding a field on that page and I remember KaiRo was against it. KaiRo?

Comment 4

[Jeromie Clark]

@laura - Oh, that's a great suggestion, thanks.  I'll double-check that it works for us this afternoon.

Comment 5

[Robert Kaiser]

Adrian, the problem is that we have requests to add at least half a dozen field to report/index, if not more, and the UI is already pretty dense. I'm not "against it" per se, I just fear that without proper planning, this already somewhat overloaded UI is getting even more and more overloaded.

Comment 6

[Benjamin Smedberg]

We should add all the fields we can and still be performance, choose a reasonable default set to display and allow users to dynamically enable/disable columns that are interesting to them.

Comment 7

[[DEACTIVATED] Adrian Gaudebert]

Benjamin, that's a pretty good idea I think. It would require more work of course, and we would develop that on the new Django UI only. I estimate it to take about 5 days of work (3 days for the first 90%, 2 days for the last 90%) + another 5 days for QA and bug fixing. 

Laura, what do you think?

Comment 8

[Robert Kaiser]

Adrian, I thought for a long time that something in the line of comment #6 would be the best target for the long term. If we can do this in socorro-crashstats and can get that into a public place relatively soon so Jeromie etc. have access, that would be great (IIUC, it passed security review so I guess it can be made public in theory).

Comment 9

[[DEACTIVATED] Adrian Gaudebert]

I believe using a combination of supersearch and report/list/ meets the requirements of this bug. You can use supersearch to search for a plugin version (for example: https://crash-stats.mozilla.com/search/?plugin_version=11.9.900.117 ), and you can now add more fields to your view of report/list/ (see at the bottom of the "Reports" tab). 

Please reopen if more is needed.