From 20811e277e61cd29ae1edc97a6c62bc1a03f442b Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Sat, 11 Aug 2001 05:26:38 +0000 Subject: Compiled HTML/TXT check-in. For some reason, it keeps thinking my darn dbschema.jpg file is changing, though. --- docs/html/quicksearch.html | 191 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 191 insertions(+) create mode 100644 docs/html/quicksearch.html (limited to 'docs/html/quicksearch.html') diff --git a/docs/html/quicksearch.html b/docs/html/quicksearch.html new file mode 100644 index 000000000..e4ff6528d --- /dev/null +++ b/docs/html/quicksearch.html @@ -0,0 +1,191 @@ +
Quicksearch is a new, experimental feature of the 2.12 release. + It consist of two Javascript files, "quicksearch.js" and + "localconfig.js", and two documentation files, + "quicksearch.html" and "quicksearchhack.html" +
The index.html page has been updated to include the QuickSearch + text box. +
To take full advantage of the query power, the Bugzilla + maintainer must edit "localconfig.js" according to the value + sets used in the local installation. +
Currently, keywords must be hard-coded in localconfig.js. If + they are not, keywords are not automatically recognized. This + means, if localconfig.js is left unconfigured, that searching + for a bug with the "foo" keyword will only find bugs with "foo" + in the summary, status whiteboard, product or component name, + but not those with the keyword "foo". +
Workarounds for Bugzilla users: +
search for '!foo' (this will find only bugs with the + keyword "foo" |
search 'foo,!foo' (equivalent to 'foo OR + keyword:foo') |
When this tool is ported from client-side JavaScript to + server-side Perl, the requirement for hard-coding keywords can + be fixed. This bug has details. +