Closed
Bug 680974
Opened 13 years ago
Closed 13 years ago
Default "report this crash" bugzilla link for fennec crash reporting shows Fennec instead of Core
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
VERIFIED
FIXED
2.5.1
People
(Reporter: nhirata, Assigned: espressive)
References
()
Details
Attachments
(3 files)
1. go to a crash signature such as https://crash-stats.mozilla.com/report/index/12c72ee6-052e-47f7-8452-b75c52110818
2. click on report this crash
Expected: Most crashes occur in Core, I would expect Core or other something more drilled down than a default of Fennec
Actual: The default is Fennec for Fennec crashes
Comment 1•13 years ago
|
||
We'd need some different rules about what crashes should go where in bugzilla by default. How would we know which Fennec crashes were not Core?
Summary: Default fennec crash reporting shows Fennec instead of Core → Default "report this crash" bugzilla link for fennec crash reporting shows Fennec instead of Core
Comment 2•13 years ago
|
||
80% or more of our crashes are not specific to what's in Firefox or Fennec, but belong mostly in Core, Toolkit, or Plugins products on Bugzilla.
I wonder if we could get this to some way where we can select one of those few and report the bug in that one.
Also, while someone is looking at this, can you change the default summary from "crash <short-signature>" to "crash in <short-signature>"?
Comment 3•13 years ago
|
||
A good guess would be to parse the file where the crash occurs and have a directory -> component mapping. if it crashes in /mozilla/netwerk/ then it should go to necko.
I'm sure that for some components (xpconnect xpcom) that wouldn't work and then we could fall back to a manual move from the person filing the bug.
Comment 4•13 years ago
|
||
That's really the only way to get even close to selecting the right component. We could probably build a big mapping from this list:
https://wiki.mozilla.org/Modules/All
but I don't know if that's worth the effort or not.
Comment 5•13 years ago
|
||
As those who file bugs from that page are usually experience people who right now often mangle the new bug URL to get into the right component, I think we don't need to build up large logic for auto-selection of a "right" product or even component. A product selection dropdown should be enough, IMHO.
Updated•13 years ago
|
Flags: in-testsuite?
Flags: in-litmus?
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
Updated•13 years ago
|
Component: General → Webapp
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → sneethling
Target Milestone: --- → 2.5.1
Assignee | ||
Comment 6•13 years ago
|
||
link to most common bugzilla products
Comment 7•13 years ago
|
||
(In reply to Schalk Neethling from comment #6)
> Created attachment 602012 [details]
> link to most common bugzilla products
Basically looks good, but the current one that has the product should be in there as well and be the first of the links.
Assignee | ||
Comment 8•13 years ago
|
||
Comment 9•13 years ago
|
||
Comment on attachment 602051 [details]
added default for current product
Yes, I like that!
(though I guess the link could in this case be just on "Firefox", and the extra space after "Firefox" isn't needed *g*)
Assignee | ||
Comment 10•13 years ago
|
||
Sent pull request :: https://github.com/mozilla/socorro/pull/405
TEST CASE
----------
Head over to report/index
The report this link should now have a link to report the bug for the current product, in core, plugins or toolkit
Assignee | ||
Comment 11•13 years ago
|
||
Updates pull request :: https://github.com/mozilla/socorro/pull/415
Comment 12•13 years ago
|
||
Commit pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/74ef4a24ce2330b45a8e2b16f09f5059f3510b9d
Merge pull request #415 from ossreleasefeed/bug680974-improve-report-this-link
provide three additional options to submit crashes to core, plugins and toolkit fixes bug 680974
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 13•13 years ago
|
||
Two very minor nits-
1. Suggestion, move the word "in" out of the <a href>. The only text that should be linked is "Firefox", "Core", "Plug-Ins", and "Toolkit"
2. Add a comma before "or" -
Change:
"Bugzilla - Report this bug in Firefox, Core, Plug-Ins or Toolkit"
To:
"Bugzilla - Report this bug in Firefox, Core, Plug-Ins, or Toolkit
Updated•13 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Whiteboard: [qa+]
Assignee | ||
Comment 14•13 years ago
|
||
Sent pull request :: https://github.com/mozilla/socorro/pull/438 adds suggestions in https://bugzilla.mozilla.org/show_bug.cgi?id=680974#c13
Comment 15•13 years ago
|
||
Commit pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/76a149820427cc46ace1a6cf5e637521150fa7fd
Merge pull request #438 from ossreleasefeed/qa-suggest-on-bug-680974
made changes as suggested by qa fixes bug 680974
Comment 16•13 years ago
|
||
Commit pushed to stage at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/da5658f7c1526b45368881a041ed217c3297f11f
made changes as suggested by qa fixes bug 680974
Updated•13 years ago
|
Whiteboard: [qa+]
You need to log in
before you can comment on or make changes to this bug.
Description
•