Normal search with "k3b" doesn't return anything: http://bugs.gentoo.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=&content=k3b But if you type it in advanced, it works: http://bugs.gentoo.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=k3b&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=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= It should return "1 bug found", bug 292281
Interesting: The "Quick Search" field in the Actions: section finds both this one and the actual k3b bug.
Also see difference of "mut" and "mutt" in "Search existing bug reports" (Non-advanced). Seems like 3 chars isn't enough to return results
(In reply to comment #2) > Also see difference of "mut" and "mutt" in "Search existing bug reports" > (Non-advanced). Seems like 3 chars isn't enough to return results The "specific" (non-advanced) content search uses the fulltext index mentioned in <http://www.bugzilla.org/docs/2.22/html/configuration.html#AEN447>. So my example with 'mut' wasn't helpful as it isn't used as a word. The "advanced" search (quicksearch is an advanced search) uses the content search only in "Advanced Searching Using Boolean Charts" as "Content matches k3b".
https://bugs.gentoo.org/buglist.cgi?quicksearch=k3b lists both this bug and the other open k3b bug.
Should be fixed now, since the search has been changed a lot between bugzilla 2 and 4. Also take a look at: https://bugs.gentoo.org/page.cgi?id=quicksearch.html
