Closed
Bug 534062
Opened 15 years ago
Closed 15 years ago
Socorro UI - needs to differentiate between empty signature types
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
1.3
People
(Reporter: lars, Assigned: ozten)
References
Details
Attachments
(1 file)
5.55 KB,
patch
|
ryansnyder
:
review+
|
Details | Diff | Splinter Review |
the UI doesn't currently differentiate between signature being null and signature being the empty string when displaying the TCBS report.
For the null case, it should display: "(null signature)" followed by a link to an explanation (http://code.google.com/p/socorro/wiki/NullOrEmptySignatures). The code that fetches the graph data for that signature should use the ##null## protocol outlined in http://code.google.com/p/socorro/wiki/TopCrashersSigHistoryAPI The link for drill down to individual crashes should take into account Bug 518144
For the empty case, it should display: "(empty signature)" followed by a link to an explanation (http://code.google.com/p/socorro/wiki/NullOrEmptySignatures). The code that fetches the graph data for that signature should use the ##empty## protocol outlined in http://code.google.com/p/socorro/wiki/TopCrashersSigHistoryAPI The link for drill down to individual crashes should take into account Bug 518144
Reporter | ||
Updated•15 years ago
|
Assignee | ||
Comment 1•15 years ago
|
||
Assignee: nobody → ozten.bugs
Attachment #417577 -
Flags: review?(ryan)
Comment 2•15 years ago
|
||
Comment on attachment 417577 [details] [diff] [review]
First attempt for empty vs null signatures
Looks good.
Might want to update the bug reference in the code - //Bug#534063 should be //Bug#534062. Might want to throw the bug title in there too, just for a quick reference.
Attachment #417577 -
Flags: review?(ryan) → review+
Assignee | ||
Comment 3•15 years ago
|
||
This is on stage now.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
You need to log in
before you can comment on or make changes to this bug.
Description
•