Closed
Bug 41655
Opened 25 years ago
Closed 14 years ago
More options on advanced querying.
Categories
(Bugzilla :: Query/Bug List, enhancement)
Tracking
()
RESOLVED
INVALID
People
(Reporter: CodeMachine, Unassigned)
References
Details
The following options would be nice in the first column.
ResolvedBy, ResolvedDate, DaysSinceResolution (for Resolved, Verified, Closed
bugs)
VerifiedBy, VerifiedDate, DaysSinceVerification (for Verified, Closed bugs)
ClosedBy, ClosedDate, DaysSinceClosure (for Closed bugs)
ReportedDate (are date comparisons supported? there's no docs on it)
Age (Days since reported)
Reporter | ||
Updated•24 years ago
|
Whiteboard: 3.2
Comment 1•24 years ago
|
||
moving to real milestones...
Whiteboard: 3.2
Target Milestone: --- → Bugzilla 3.2
Reporter | ||
Comment 2•23 years ago
|
||
Moving to new Bugzilla product ...
Assignee: tara → endico
Component: Bugzilla → Query/Bug List
Product: Webtools → Bugzilla
Version: other → 2.13
Updated•21 years ago
|
Assignee: endico → nobody
Updated•19 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Comment 3•17 years ago
|
||
Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?". Then, either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.
This particular bug has not been touched in over eight months, and thus is being retargeted to "---" instead of "Bugzilla 4.0". If you believe this is a mistake, feel free to retarget it to Bugzilla 4.0.
Target Milestone: Bugzilla 3.2 → ---
Updated•16 years ago
|
Assignee: nobody → query-and-buglist
Priority: P3 → --
Comment 4•14 years ago
|
||
This is a lot of different stuff in one request. There are no votes and no CCs. Also, I suspect that future improvements will automatically allow a lot of this stuff to be done.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•