diff options
| author | cyeh%bluemartini.com <> | 2001-03-01 08:07:24 +0100 |
|---|---|---|
| committer | cyeh%bluemartini.com <> | 2001-03-01 08:07:24 +0100 |
| commit | 5b2994b0ce4cf27709b3742a2b63a680464662a0 (patch) | |
| tree | ac2b46dde7b3a19475df1a8400e99bc3c120e283 /quicksearch.html | |
| parent | d0605ef9490b55c38d090c21b5993eda143e7e86 (diff) | |
| download | bugzilla-5b2994b0ce4cf27709b3742a2b63a680464662a0.tar.gz bugzilla-5b2994b0ce4cf27709b3742a2b63a680464662a0.tar.xz | |
fix for 69793: check in new files for QuickSearch
patch contributed by franke@ags.uni-sb.de (Andreas Franke)
Now add quicksearch functionality to the main index page.
Diffstat (limited to 'quicksearch.html')
| -rw-r--r-- | quicksearch.html | 146 |
1 files changed, 146 insertions, 0 deletions
diff --git a/quicksearch.html b/quicksearch.html new file mode 100644 index 000000000..900180065 --- /dev/null +++ b/quicksearch.html @@ -0,0 +1,146 @@ +<html> +<head> + <title>Bugzilla QuickSearch</title> +</head> + +<body bgcolor="#ffffff"> + +<small>If you are already familiar with the original +<a href="query.cgi">Bugzilla Query Form</a>, +you may prefer <a href="quicksearchhack.html">this form</a>. +</small> + +<p> +<script src="localconfig.js"></script> +<script src="quicksearch.js"></script> + +<h1>Bugzilla QuickSearch</h1> + +Type in one or more words (or word fragments) to search for: + +<!-- The name of the form must be "f" (used in "quicksearch.js"). --> + +<form name="f" action="show_bug.cgi" method="get" + onsubmit="QuickSearch(); return false;"> + <table> + <tr> + <td><input type="text" size="40" name="id"/></td> + <td align=left><input type="submit" value="Search"/></td> + <!-- <td><a href="javascript:QuickSearch_Help();">[Help]</a></td> --> + </tr> + </table> +</form> + +<script> +<!-- +document.forms['f'].id.focus(); +//--> +</script> + +<p> +<h2>Getting Started</h2> + +<ul> +<li> This is <b>case-insensitive</b> search. + <ul> + <li> <tt>table</tt> , <tt>Table</tt> + and <tt>TABLE</tt> are all the same. + </ul> +<li> This is <b>all words as substrings</b> search.<br> + Therefore you should <b>use stems</b> to get better results: + <ul> + <li> Use <tt>localiz</tt> instead of <tt>localize</tt> or + <tt>localization</tt>. + <li> Use <tt>bookmark</tt> instead of <tt>bookmarks</tt> or + <tt>bookmarking</tt>. + </ul> +</ul> + +<a name="features"/> +<h2>Features</h2> + +<ul> +<li> Boolean operations: ``<tt>-foo</tt>''(NOT), ``<tt>foo bar</tt>''(AND), + ``<tt>foo|bar</tt>''(OR). + <ul> + <li> <b>NOT</b>: Use <tt><b>-</b><i>foo</i></tt> to exclude bugs + with <tt><i>foo</i></tt> in the summary. + <li> <b>AND</b>: Space-separated words are treated as a conjunction. + <li> <b>OR</b>: Within a word, "|"-separated parts denote alternatives. + <li> Besides "|", a comma can be used to separate alternatives. + <li> OR has higher precedence than AND; AND is the top level operation + </ul> + <i>Example:</i> <tt>url,location bar,field -focus</tt> + means + <nobr>(<tt>url</tt> OR <tt>location</tt>) AND (<tt>bar</tt> OR <tt>field</tt>) AND (NOT <tt>focus</tt>)</nobr> + <p> +<li> Use <tt>+foo</tt> to search for bugs where the <b>summary</b> contains <tt>foo</tt> as a <b>substring</b>.<br> + Use <tt>#foo</tt> to search for bugs where the <b>summary</b> contains the <b>word</b> <tt>foo</tt> + <ul> + <li> <tt>+brow</tt> does not find all bugs in the <tt>Browser</tt> product + <li> <tt>#title</tt> does not find bugs bugs with <tt>titlebar</tt> or <tt>titled</tt> + </ul> + Phrases with special chars (space, comma, +, -, #, ...) can be <b>quoted</b>: + <ul> + <li> <tt>"lock icon"</tt> + </ul> +<p> +<li> <b>Open vs. Resolved Bugs</b>:<br> + By default, only open (i.e. unresolved) bugs are shown. + Use <tt>+DUP</tt> as first word in your query + to include duplicate bugs in your search, + <tt>FIXED</tt> to search for fixed bugs only, + or <tt>ALL</tt> to search all bugs, + regardless of status or resolution. Searching for duplicates is + recommended if you can't find an open bug directly. + <ul> + <li> <tt>+DUP,FIXED table border</tt> + <li> <tt>ALL mouse wheel</tt> + </ul> +<p> +<li> <b>Focus the Search with Products & Components</b>:<br> + To search for bugs in product "Foo Bar" only, add + <tt>:foo</tt> or <tt>:bar</tt> or both + to your query. + You can do this with any substring of a + <a href="describecomponents.cgi">product or component</a> + to focus the search. +</ul> + +<h2>More Tips</h2> + +<ul> +<li> You can also use this tool to <b>lookup</b> a bug by its number. + <ul> + <li> <tt>12345</tt> + </ul> +<li> A comma-separated list of bug numbers gives you a list of these bugs. + <ul> + <li> <tt>12345,23456,34567</tt> + </ul> +</ul> + +<p> +By default, the following fields are searched: Summary, Keywords, Product, +Component, Status Whiteboard. If a word looks like a part of a URL, that field +is included in the search, too. +<p> +<!-- +<small>For further details, see +<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=61561">Bug 61561</a> and +<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=69793">Bug 69793</a>. +</small> + --> +<hr> + +Use the powerful +<a href="query.cgi">Bugzilla Query Form</a> +for advanced queries. + +</body> +</html> + + + + + |