1054282 - Expose topcrasher_ranks_bybug report to users

Status: RESOLVED WONTFIX

(Socorro :: Webapp, task)

Description

[Schalk Neethling [:espressive]]

Currently there is no way from the UI to access the topcrasher ranks bybug report, a user basically needs to know the URL.

One suggestions has been:

"In terms of exposing it on the front end, I was thinking that anywhere (or perhaps just on top crashers) bug numbers are listed and clickable, we can show a little context menu, on click, that offers two options:

=> View Bug on Bugzilla
=> View Signatures for Bug"

KaiRo has replied and does not believe this will work and might actually negatively effect their workflow.

KaiRo has an different idea:

"I'd love to see this report exposed on Bugzilla, actually, on any bug that has the "Crash Signature" field filled."

Thoughts, suggestions welcome.

Comment 1

[Robert Kaiser]

(In reply to Schalk Neethling [:espressive] from comment #0)
> KaiRo has replied and does not believe this will work and might actually
> negatively effect their workflow.

Just to expand on why I think it might negatively affect workflow: We are calling up the bugs for crashes a lot from reports, we need the topcrasher_ranks_bybug way more rarely - usually mainly for either verifying if the crashes for a bug still happen or what their status on various channels is (which both are actions we do after/when looking at a bug in Bugzilla).

Comment 2

[Robert Kaiser]

Also, we probably need the speed and for sure some correctness/usability issues with the report fixed before we can expose it, so marking those bugs as blockers.

Comment 3

[Schalk Neethling [:espressive]]

I am guessing this is still hiding behind a flag or known url and it is going to stay that way for a while?

Comment 4

[Robert Helmer [:rhelmer]]

(In reply to Schalk Neethling [:espressive] from comment #3)
> I am guessing this is still hiding behind a flag or known url and it is
> going to stay that way for a while?

Not sure how useful this report is in its current form, I'll find out.

Comment 5

[[DEACTIVATED] Adrian Gaudebert]

KaiRo, is this report actually used at all? Our analytics says it has one single view in the last 5 months. 

Can we kill it? :)

Comment 6

[Robert Kaiser]

We talked about this in person at Mozlando - this is something still very much wanted and useful but the issue was and is that it's quite slow so we didn't put it into more widely exposed production. We should get a new version in place that is easier to handle and then get it exposed somehow. It's very useful to have something in place that can tell us "is this bug still relevant, and if so, how much?" - exposing percentage of this signature among crashes per product version is even more helpful that crash rank, I hope we can achieve that.

Comment 7

[[DEACTIVATED] Adrian Gaudebert]

So I made this little service to replace the one we have in Socorro: https://adngdb.github.io/bug-signatures-status/

We should now decide if it's good enough, if we can subsequently remove the existing code from Socorro, and how we can expose this service to our users (simply to make it discoverable, which it is not at the moment).

Comment 8

[Robert Kaiser]

This new service should run on Socorro proper, I don't trust things for the long haul which run on personal spaces over which Mozilla has no control.

Comment 9

[[DEACTIVATED] Adrian Gaudebert]

I'm closing this bug in favor of 1252059.