Closed
Bug 794548
Opened 13 years ago
Closed 11 years ago
display "exploitability" rating in UI to logged-in users
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
77
People
(Reporter: ted, Assigned: peterbe)
References
Details
Attachments
(2 files)
In bug 794540 we'd like to add an "exploitability" field to the processed JSON. This is somewhat sensitive information, so we'd like to expose it only to logged-in users.
Comment 1•12 years ago
|
||
Just exposing this value in an individual crash's page is likely insufficient. Is there to be reports based on this value? I'm imagining that it would be nice to have the value available as a search parameter, too.
We need to know what you want us to do with this value besides just store it.
Reporter | ||
Comment 2•12 years ago
|
||
I don't know that it's all that useful as a search parameter. It'd probably be useful to have reports based on this. Having it displayed on the report index page for logged-in users is pretty much the minimal effort we can do here.
davidb: do you have thoughts on this?
Comment 3•12 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #2)
> I don't know that it's all that useful as a search parameter. It'd probably
> be useful to have reports based on this. Having it displayed on the report
> index page for logged-in users is pretty much the minimal effort we can do
> here.
>
> davidb: do you have thoughts on this?
Searching is a nice to have but I wouldn't slow down for it.
Comment 4•12 years ago
|
||
I think for the first iteration, let's just get it into the individual crash report display (for logged-in only). Having it in the db makes it available for running ad hoc queries, too.
Comment 5•12 years ago
|
||
Given the timing here and how simple this bug is, I think we should do it in both PHP and Django, fwiw
Updated•12 years ago
|
QA Contact: laura
Target Milestone: --- → 28
Comment 6•12 years ago
|
||
PR for PHP
https://github.com/mozilla/socorro/pull/960
Comment 7•12 years ago
|
||
Commits pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/ee01bd9f91cb8f6d712819c54a0cea4e00dc56e6
Fixes bug 794548, expose exploitability attribute in the UI to logged in users
https://github.com/mozilla/socorro/commit/c5cf4b36e4c381ce163f23823ea1945957271e1a
Merge pull request #960 from lauraxt/794548
Fixes bug 794548, expose exploitability attribute in the UI to logged in...
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Assignee: nobody → laura
Comment 8•12 years ago
|
||
This was hard to test without data, and apparently I messed it up. I thought the exploitability value was in the processed JSON, but apparently it's only in PostgreSQL. Back to the drawing board a little, because nothing else on that page comes from PG. Reopening.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•12 years ago
|
Target Milestone: 28 → 29
Comment 9•12 years ago
|
||
This worked initially, was just missing data from the middleware. Fixed with bug 815309.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Comment 10•12 years ago
|
||
QA test should be to be able to see Exploitability field when looking at an individual bug.
Comment 11•12 years ago
|
||
QA verified on stage - the new exploitability field is only visible when logged in with an admin account.
Example crash
https://crash-stats.allizom.org/report/index/c68b329d-833c-4d18-82b1-a79c32121129
Status: RESOLVED → VERIFIED
Comment 12•12 years ago
|
||
QA verified on prod
Comment 14•12 years ago
|
||
THANK YOU! \o/
Assignee | ||
Comment 15•11 years ago
|
||
This regressed when we moved to Django.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 16•11 years ago
|
||
Assignee | ||
Updated•11 years ago
|
Assignee: laura → peterbe
Assignee | ||
Comment 18•11 years ago
|
||
Apparently, for new crashes this information is in the HBase processed JSON under the key "sensitive". So we don't need to do depend on 948533 because supposedly, it's there.
It might be that we don't always get it but for new crashes we should.
(at the time of writing I've not been able to test any recent crashes through HBase on stage to see if it's really there)
No longer depends on: 959295
Assignee | ||
Comment 19•11 years ago
|
||
Comment 20•11 years ago
|
||
Commit pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/f903be1eb0473272662f9adb12e1ec2ae26e76e1
fixes bug 794548 - display "exploitability" rating in UI to logged-in users, r=rhelmer,AdrianGaudebert
Updated•11 years ago
|
Status: REOPENED → RESOLVED
Closed: 12 years ago → 11 years ago
Resolution: --- → FIXED
Comment 21•11 years ago
|
||
Commit pushed to master at https://github.com/mozilla/socorro
https://github.com/mozilla/socorro/commit/f903be1eb0473272662f9adb12e1ec2ae26e76e1
fixes bug 794548 - display "exploitability" rating in UI to logged-in users, r=rhelmer,AdrianGaudebert
Updated•11 years ago
|
Target Milestone: 29 → 77
You need to log in
before you can comment on or make changes to this bug.
Description
•