Closed
Bug 43551
Opened 24 years ago
Closed 21 years ago
bugzilla handles "days since last changed" incorrectly
Categories
(Bugzilla :: Query/Bug List, defect, P2)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: qaz2, Assigned: endico)
References
()
Details
From Bugzilla Helper: User-Agent: Mozilla/4.06 (Macintosh; I; PPC, Nav) BuildID: If you search for all bugs, with less than X days since last changed, Bugzilla does not check the year. Thus, if i search on June 25 for all bugs changed within the last 5 days, I will get bugs from June 21-25, 1999, 1998, etc. as well as those from June 21-25, 2000. Reproducible: Always Steps to Reproduce: 1.Go to the Bugzilla Query Page 2.Search for all bugs with days since bug changed < 5. 3.Look at the results. There will be some bugs from 1999. Actual Results: Some bugs from 1999. Expected Results: Only bugs from 2000. Probably just Bugzilla ignoring the year, though it could POSSIBLY be a Y2K problem.
Comment 1•24 years ago
|
||
I can't reproduce this, and everything looks right in a quick scan of the source code. If you're still having problems, can you please post a URL that demonstrates this problem? Also, let me know where you're seeing the problems and what columns you're viewing on the bug list.
URL added. Click on one of the bugs at the top, and notice that the bug was last changed around this time in a previous year. I am using default columns.
For me, the days since last changed option just doesn't work at all. For example, the following two queries give exactly the same result: http://bugzilla.mozilla.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&resolution=FIXED&changedin=1&chfield=resolution&chfieldvalue=fixed&cmdtype=doit&order=Reuse+same+sort+as+last+time http://bugzilla.mozilla.org/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&resolution=FIXED&changedin=5&chfield=resolution&chfieldvalue=fixed&cmdtype=doit&order=Reuse+same+sort+as+last+time Which should return bugs fixed in the last 1 and 5 days respectively.
Comment 4•23 years ago
|
||
worksforme with bugzilla.mozilla.org which was upgraded (I believe to the tip) on 6/13. I can't remember this ever not working as expected.
Updated•23 years ago
|
Priority: P3 → P2
Target Milestone: --- → Bugzilla 2.16
Comment 5•23 years ago
|
||
moving
Assignee: tara → endico
Component: Bugzilla → Query/Bug List
Product: Webtools → Bugzilla
Version: other → 2.10
Len, I am seeing the same thing. I have a saved query which I named "Recent Fixes" which searches for exactly: Resolution = Fixed Changed in the last 0 days Sort by Last Changed I was missing a lot of late-night fixes, so I decided to look at changes in the last 1 days, instead. I saved the new query over the old one, but the results page is still giving results as if the setting was 0. Same applies if I try larger values. The value *is* being saved into the saved query by Bugzilla, but has no impact on the results, which is really strange... I tried to reproduce the behavior from scratch on a new saved query called "Foobar", but everything worked as it should have. I could update it, and the results updated. Len, were you getting this behavior for queries that weren't saved? Could this have anything to do with multi-word saved queries?
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
|
||
Anyone still seeing this problem? Gerv
Comment 9•22 years ago
|
||
Yeah, there are issues to do with this. Can't remember them off hand, but the 'from date' defaulting to 'today' is one problem, at least.
Comment 10•22 years ago
|
||
URL that should give bugs less than 100 not changed in last 365 days: http://bugzilla.mozilla.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&remaction=run&namedcmd=Quality+Assurance&order=Reuse+same+sort+as+last+time&field0-0-0=bug_id&type0-0-0=lessthan&value0-0-0=1000&field0-1-0=%28to_days%28now%28%29%29+-+to_days%28bugs.delta_ts%29%29&type0-1-0=greaterthan&value0-1-0=365 Result: 0 URL that should give bugs less than 100: http://bugzilla.mozilla.org/buglist.cgi?query_format=&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&emailassigned_to1=1&emailtype1=exact&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailtype2=exact&email2=&bugidtype=include&bug_id=&votes=&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&remaction=run&namedcmd=Quality+Assurance&order=Bug+Number&field0-0-0=bug_id&type0-0-0=lessthan&value0-0-0=1000 Result: lots Bug 228 which appears in second list should appear in first as well.
Comment 11•21 years ago
|
||
All remaining issues must now have gone away with the fixing of bug 37749.
Comment 12•21 years ago
|
||
Marking fixed per comment 11. If anyone is still running into this with a cvs-tip Bugzilla (that's NOT bugzilla.mozilla.org at the moment), please reopen. bugzilla.mozilla.org should pick this up next time they upgrade.
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•