Closed
Bug 620031
Opened 14 years ago
Closed 14 years ago
bug lists should be in sortable tables
Categories
(Tree Management Graveyard :: OrangeFactor, defect, P1)
Tree Management Graveyard
OrangeFactor
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: k0scist, Unassigned)
References
Details
Attachments
(1 file, 1 obsolete file)
100.84 KB,
patch
|
jmaher
:
review+
|
Details | Diff | Splinter Review |
Lists of bugs appear in several places on the site. In each of these views, the same functions/markup should be used. They should be in a sortable table using jquery dataTables (http://www.datatables.net/). Columns should be: - bug id (strike out if closed) - the bug count - the bug summary - links to the bug data and the bugzilla page In addition, things like OS, etc could be displayed if applicable.
Assignee | ||
Comment 2•14 years ago
|
||
Also, some of these tables, such as the one on Bug Count, take a while to load. There should be a generic "Loading" message for all tables before they're populated, like the one I added to Bug Count.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → mcote
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•14 years ago
|
||
This replaces all tables with fancy jquery DataTables. This has built in pagination and sorting, and just plain looks nice. I centralized the bug-count tables (used in the BugCount, TestRun, TopBugs, and Simulator views) in one function, bugDetailsTable(), with a convenience function, simpleBugDetailsTable(), for use with data returned by the bug_simple db view. I removed the test-type info from BugCount and TestRun, since it didn't seem very useful. I can add more columns later if needed. The links to details and bugzilla are hover-over links, because having buttons/links on every row of a table is awful. The options are either making the bug-id column look a little unnaturally wide or having it resize when moused-over, neither of which I particularly like, but I went with the former. A shorter way of presenting the links (currently "[details] [bugzilla]") would mitigate this, if we can think of a way (images with tooltips or some such). Other little fixes: - spaced the top page title a bit further from the menu - fixed the menu-creation code that somehow ran on couch but nowhere else - don't include an empty object in parseBugs() when the occurrence is outside the given date range - fixed first- and last-occurrence date calculation in parseBugs() (though it may not even be used anymore)
Attachment #501435 -
Flags: review?(jmaher)
Assignee | ||
Comment 4•14 years ago
|
||
Accidentally left in some console calls.
Attachment #501435 -
Attachment is obsolete: true
Attachment #501437 -
Flags: review?(jmaher)
Attachment #501435 -
Flags: review?(jmaher)
Assignee | ||
Updated•14 years ago
|
Priority: -- → P1
Comment 5•14 years ago
|
||
Comment on attachment 501437 [details] [diff] [review] Use jquery DataTables when displaying bug info and other tabular data hard to tell if I am overlooking anything here, but this patch does a good job of cleaning up more of the code (removing a lot of hardcoded html stuff) and putting the bug display into a single function.
Attachment #501437 -
Flags: review?(jmaher) → review+
Assignee | ||
Comment 6•14 years ago
|
||
Pushed as http://hg.mozilla.org/automation/orangefactor/rev/379ce1e9f981
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Product: Testing → Tree Management
Updated•4 years ago
|
Product: Tree Management → Tree Management Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•