Closed Bug 572940 Opened 15 years ago Closed 14 years ago

A field must be specified when looking for changes in some given time frame

Categories

(Bugzilla :: Query/Bug List, defect)

3.4.6
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: nelson, Unassigned)

References

()

Details

There were numerous NSS bugs worked on in calendar 2005, 2006 and 2007 for which CVS- vulnerability numbers were assigned. Those bugs have comments that bear the string of the CVE number. One example is bug 330114 which bears a comment with this line: Related to CVE-2006-4340 : unchecked garbage in PKCS v1.5 blocks Yet a search for all NSS bugs modified between 1-Jan-2005 and 1-Jan-2008 bearing the string CVE-20 consistently finds NO bugs at all! Consequently I spent over an hour searching for a bug that should have been found in just minutes. Here's a sample search that produces empty results, but shouldn't. https://bugzilla.mozilla.org/buglist.cgi?chfieldto=2008-01-01&query_format=advanced&order=Bug%20Number&chfieldfrom=2005-01-01&longdesc=CVE-20&longdesc_type=substring&product=NSS
This isn't a BMO issue. You can't really use chfieldfrom and chfieldto without a chfield... Notice that this works just fine: https://bugzilla.mozilla.org/buglist.cgi?chfieldto=2008-01-01&query_format=advanced&chfield=[Bug%20creation]&chfieldfrom=2005-01-01&longdesc=CVE-20&product=NSS&longdesc_type=substring
Assignee: nobody → query-and-buglist
Component: Bugzilla: Other b.m.o Issues → Query/Bug List
Product: mozilla.org → Bugzilla
QA Contact: other-bmo-issues → default-qa
Version: other → 3.4.6
I see, but I'm looking for bugs that experienced ANY change at all during those years.
Severity: major → normal
WFM in Bugzilla 4.0. No idea which bug fixed the problem.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
Summary: BMO search finds no NSS bugs with "CVE-20" in a comment → A field must be specified when looking for changes in some given time frame
You need to log in before you can comment on or make changes to this bug.