quicksearch.html.tmpl 5.6 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
[%# 1.0@bugzilla.org %]
[%# The contents of this file are subject to the Mozilla Public
  # License Version 1.1 (the "License"); you may not use this file
  # except in compliance with the License. You may obtain a copy of
  # the License at http://www.mozilla.org/MPL/
  #
  # Software distributed under the License is distributed on an "AS
  # IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or
  # implied. See the License for the specific language governing
  # rights and limitations under the License.
  #
  # The Original Code is the Bugzilla Bug Tracking System.
  #
  # Contributor(s): N.N.
  #                 Marc Schumann <wurblzap@gmail.com>
  #%]

[% PROCESS global/variables.none.tmpl %]

[% INCLUDE global/header.html.tmpl
   title  = "$terms.Bugzilla QuickSearch",
   style  = 'ul {margin-bottom: 2ex}
             ul li {margin-top: 2ex}
             ul li ul li {margin-top: 0}'
   onload = 'document.forms[\'f\'].quicksearch.focus()'
 %]

<p style="font-size: 80%">
  If you are already familiar with the original
  <a href="query.cgi">[% terms.Bugzilla %] Search Form</a>,
  you may prefer <a href="page.cgi?id=quicksearchhack.html">this form</a>.
</p>

<p>
  Type in one or more words (or word fragments) to search for:
</p>

<form name="f" action="buglist.cgi" method="get"
      onsubmit="if (this.quicksearch.value == '')
                { alert('Please enter one or more search terms first.');
                  return false; } return true;">
  <input type="text" size="40" name="quicksearch">
43
  <input type="submit" value="Find" id="find">
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190
</form>

<h2>Getting Started</h2>

<ul>
  <li>
    This is <strong>case-insensitive</strong> search:<br />
    <ul>
      <li><tt>table</tt>, <tt>Table</tt> and <tt>TABLE</tt> are all the same.</li>
    </ul>
  </li>
  <li>
    This is <strong>all words as substrings</strong>
    search.<br />
    Therefore you should <strong>use stems</strong> to get better results:
    <ul>
      <li>
        Use <tt>localiz</tt> instead of <tt>localize</tt> or
        <tt>localization</tt>.
      </li>
     <li>
       Use <tt>bookmark</tt> instead of <tt>bookmarks</tt> or
       <tt>bookmarking</tt>.
     </li>
   </ul>
  </li>
</ul>

<h2><a name="features">Features</a></h2>

<ul>
  <li>
    Boolean operations: &ldquo;<tt>-foo</tt>&rdquo;&nbsp;(NOT),
    &ldquo;<tt>foo&nbsp;bar</tt>&rdquo;&nbsp;(AND),
    &ldquo;<tt>foo|bar</tt>&rdquo;&nbsp;(OR).
    <ul>
      <li>
        <strong>NOT</strong>:<br />
        Use <tt><b>-</b><i>foo</i></tt> to exclude [% terms.bugs %]
        with <tt><i>foo</i></tt> in the summary.
      </li>
      <li>
        <strong>AND</strong>:<br />
        Space-separated words are treated as a conjunction.
      </li>
      <li>
        <strong>OR</strong>:<br />
        Within a word, "|"-separated parts denote alternatives.
      </li>
      <li>
        Besides "|", a comma can be used to separate alternatives.
      </li>
      <li>
        OR has higher precedence than AND; AND is the top level operation.
      </li>
    </ul>
    <i>Example:</i>
    <tt>url,location bar,field -focus</tt> means
    (<tt>url</tt> OR <tt>location</tt>) AND (<tt>bar</tt> OR <tt>field</tt>)
    AND (NOT <tt>focus</tt>)
  </li>
  <li>
    Use <tt>+foo</tt> to search for [% terms.bugs %] where the
    <strong>summary</strong> contains <tt>foo</tt> as a
    <strong>substring</strong>.<br/>
    Use <tt>#foo</tt> to search for [% terms.bugs %] where the
    <strong>summary</strong> contains the <strong>word</strong> <tt>foo</tt>.
    <ul>
      <li>
        <tt>+brow</tt> does not find all [% terms.bugs %] in the
        <tt>Browser</tt> product.
      </li>
      <li>
        <tt>#title</tt> does not find [% terms.bugs %] with <tt>titlebar</tt>
        or <tt>titled</tt>.
      </li>
    </ul>
    Phrases with special chars (space, comma, +, -, #, &hellip;) can be
    <strong>quoted</strong>:
    <ul>
      <li>
        <tt>"lock icon"</tt>
      </li>
    </ul>
  </li>
  <li>
    <strong>Open vs. Resolved [% terms.Bugs %]</strong>:<br />
    By default, only open (i.e. unresolved) [% terms.bugs %] are shown.
    Use <tt>+DUP</tt> as first word in your search to include duplicate
    [%+ terms.bugs %] in your search,
    <tt>FIXED</tt> to search for fixed [%+ terms.bugs %] only,
    or <tt>ALL</tt> to search all [% terms.bugs %],
    regardless of status or resolution.
    Searching for duplicates is recommended if you can't find an open
    [%+ terms.bug %] directly.
    <ul>
      <li>
        <tt>+DUP,FIXED table border</tt>
      </li>
      <li>
        <tt>ALL mouse wheel</tt>
      </li>
    </ul>
  </li>
  <li>
    <strong>Focus the Search with Products &amp;
    Components</strong>:<br />
    To search for [% terms.bugs %] in product "Foo Bar" only, add
    <tt>:foo</tt> or <tt>:bar</tt> or both to your search.
    You can do this with any substring of a
    <a href="describecomponents.cgi">product or component</a> to focus the
    search.
  </li>
</ul>

<h2>More Tips</h2>

<ul>
  <li>
    You can also use this tool to <strong>lookup</strong> a [% terms.bug %] by
    its number:<br />
    <ul>
      <li><tt>12345</tt></li>
    </ul>
  </li>
  <li>
    A comma-separated list of [% terms.bug %] numbers gives you a list of these
    [%+ terms.bugs %]:<br />
    <ul>
      <li><tt>12345,23456,34567</tt></li>
    </ul>
  </li>
</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>
<hr>

<p>
  Use the powerful <a href="query.cgi">[% terms.Bugzilla %] Search Form</a>
  for advanced queries.
</p>

[% PROCESS global/footer.html.tmpl %]