Closed
Bug 58179
Opened 24 years ago
Closed 12 years ago
End date not included in queries
Categories
(Bugzilla :: Query/Bug List, defect, P2)
Bugzilla
Query/Bug List
Tracking
()
RESOLVED
FIXED
Bugzilla 4.2
People
(Reporter: curt, Assigned: LpSolit)
References
Details
Attachments
(1 file, 2 obsolete files)
918 bytes,
patch
|
dkl
:
review+
|
Details | Diff | Splinter Review |
When querying for bugs across a range of dates the last date is not included in the results. This is probably not what the user would expect.
Reporter | ||
Comment 1•24 years ago
|
||
Updated•24 years ago
|
Comment 2•24 years ago
|
||
Won't this patch break it if the user specifies a specific time instead of just a date?
Comment 3•23 years ago
|
||
Hmm, yeah. An unspecified time should convert to either 12:00am or 11:59pm depending on what field it's in.
Target Milestone: --- → Bugzilla 2.16
Updated•23 years ago
|
Priority: P3 → P2
Comment 4•23 years ago
|
||
-> New Bugzilla Product
Assignee: tara → justdave
Component: Bugzilla → Administration
Product: Webtools → Bugzilla
Version: other → unspecified
Comment 5•23 years ago
|
||
Wrong Component
Assignee: justdave → endico
Component: Administration → Query/Bug List
Comment 6•23 years ago
|
||
Removing patch keyword; Dave found problems with it. We need a fixed version. Gerv
Comment 7•23 years ago
|
||
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 8•22 years ago
|
||
*** Bug 145450 has been marked as a duplicate of this bug. ***
Updated•22 years ago
|
Attachment #18115 -
Attachment is obsolete: true
Comment 9•21 years ago
|
||
This patch fixes the date range in the "Bug Changes" box. I have not looked at the date ranges in the "Boolean Charts".
Updated•21 years ago
|
Assignee: endico → nobody
Comment 10•20 years ago
|
||
These bugs appear to be abandoned. Retargeting to 2.20
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Comment 11•19 years ago
|
||
Hey Joel, have you fixed this already, or will your sqlifyDate cleanup fix this?
Hardware: PC → All
Comment 12•19 years ago
|
||
No. It is still <= 0000 on the day specificed rather than <= 2359 on the day specified. Steve's approach is probably a decent way to do it, but we should check the cross-db stuff too. We need to go through the code and makes sure that all calls to sqlifydate know which way they are comparing and make it consistent.
Comment 13•19 years ago
|
||
Comment on attachment 128192 [details] [diff] [review] Add option to SqlifyDate to add a day Hit by bitrot...
Attachment #128192 -
Flags: review-
Assignee | ||
Comment 14•18 years ago
|
||
Only security and dataloss fixes will be accepted on the 2.20 branch.
Assignee: nobody → query-and-buglist
Severity: normal → minor
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.20 → ---
Comment 15•18 years ago
|
||
(In reply to comment #14) > Only security and dataloss fixes will be accepted on the 2.20 branch. Is 'Zarro Boogs found.' on a search that should yield results not considered data loss? As mentioned in Bug 145450 (Dupe of this) entering an end date ('2006-11-24') completely breaks the search. I recently did a Search for a Bug that I had read a user had filed on a specific date, but I did not know its #. Guesing a probable keyword and entering the date in both fields of the 'changed between', I netted 'Zarro Boogs found'. I tried again and again, wasting probably 10 minutes trying different keywords, date ranges and selected search items - all to no avail. Yet I take out the end date from the search and there it is. This is a simple problem wit what should be a very simple solution, yet the Bug is 6 YEARS and 1 month old now. That's shocking, and sad.
Comment 16•15 years ago
|
||
The bug is still around in Bugzilla.Mozilla.org as of today. pi
Severity: minor → normal
Comment 17•14 years ago
|
||
We should probably fix this, but if we do, the UI needs to be changed to say "through" instead of "to", if it says "to" anywhere.
Assignee | ||
Comment 21•12 years ago
|
||
Assignee: query-and-buglist → LpSolit
Attachment #128192 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #611034 -
Flags: review?(dkl)
Comment 22•12 years ago
|
||
Comment on attachment 611034 [details] [diff] [review] patch, v1 Review of attachment 611034 [details] [diff] [review]: ----------------------------------------------------------------- Looks good. r=dkl
Attachment #611034 -
Flags: review?(dkl) → review+
Assignee | ||
Updated•12 years ago
|
Flags: approval4.2+
Flags: approval+
Assignee | ||
Comment 23•12 years ago
|
||
11.5 years to fix this bug. :-/ Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/trunk/ modified Bugzilla/Search.pm Committed revision 8174. Committing to: bzr+ssh://lpsolit%40gmail.com@bzr.mozilla.org/bugzilla/4.2/ modified Bugzilla/Search.pm Committed revision 8063.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•