Closed Bug 248650 Opened 20 years ago Closed 19 years ago

Performing a quick search only finds exact matches

Categories

(Thunderbird :: Address Book, enhancement)

x86
Windows XP
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 123788

People

(Reporter: Frank.Swasey, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124 Build Identifier: Thunderbird 0.7 It would be a nice feature to add if spaces in the quick search box were converted to asterisks because managers like to search for "firstname lastname' and cannot seem to understand that the HR system is loading the LDAP directory with middle names and initials. Reproducible: Always Steps to Reproduce: 1.Set up an LDAP entry with a name of "John Q. Public" 2.Open the Address book and select the LDAP directory 3.Do a quick search for "John Public" Actual Results: No Entries Found because the software searched for "*John Public*" Expected Results: Found the entry for "John Q. Public" by searching for "*John*Public*"
Adding wildcards (esp. on the front of a string) has performance implications for a large LDAP directory. At most this should be configurable and turned off by default. Providing separate boxes for first and last name, and educating users about wildcards, would be better IMO.
I'm not asking that wildcards be added to the front and end of the string (they are already there). I'm asking that (even if it's just an option) spaces in the quick search string be replaced with asterisks so people will have better luck finding matches. The default quick search performed by outlook and apple mail breaks the quick search string up at the word boundaries and performs a complex search to find the entry or entries that have all the individual words in the specified attribute. If the attribute is properly indexed the wildcard search is really not that expensive.
Seamonkey bug 123788.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
So, you are equating a feature request with a bug? Or are you saying that you have no interest in fulfilling the request?
Duping this, because the functionality is Core, even tho the "Mailnews:Search" bug category is filed under "Suite." *** This bug has been marked as a duplicate of 123788 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.