Closed Bug 611645 Opened 15 years ago Closed 14 years ago

Search feature has logical error

Categories

(Bugzilla :: Bugzilla-General, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: m.staberock, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de-de; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 (.NET CLR 3.5.30729) Build Identifier: The search for two words, entered in the search box, should always be and AND search by default, like with search machines (Google), not an OR search. Also, typing for example "window AND title" (without the quotation marks of course) does not find bug summaries with "window" and "title", but any of them. If the combination of both word should not be found, the result should say so. Reproducible: Always Steps to Reproduce: 1. Enter "window" and "title" in the search box, seperated by a space, without quotation marks. It loads a huge number of results with either "window" or "title" 2. 3. Actual Results: Too many wrong results. Expected Results: Results where both words are in the bug summary.
Okay. Which search box? There are several different types of search in Bugzilla.
OS: Windows 7 → All
Hardware: x86 → All
(In reply to comment #0) > The search for two words, entered in the search box, should always be and AND > search by default, like with search machines (Google) Google doesn't do an AND search. AFAIK, results are based on some global score, pretty much as the default searches on Bugzilla work. IMO a dupe of bug 607332.
(In reply to comment #2) > Google doesn't do an AND search. Yes it does, more or less. And it's the behavior that people expect. Anyhow, I need to know which search box the reporter is using before I can say that this is a duplicate of the other bug.
Almost a year without a response so it's higly likely that the reporter is unresponsive. Please, feel free to reopen if the question is ever answered. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.