aboutsummaryrefslogtreecommitdiffstats
path: root/quicksearch.html
blob: df7e85ccf006536aacfdf8ab240273f025ceec27 (plain)
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
43
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
<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:

<form name="f" action="show_bug.cgi" method="get"
      onsubmit="QuickSearch(f.id.value); 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> &nbsp;<tt>table</tt>&nbsp;, &nbsp;<tt>Table</tt>&nbsp; 
     and &nbsp;<tt>TABLE</tt>&nbsp; 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 &nbsp;<tt><b>-</b><i>foo</i></tt>&nbsp; to exclude bugs 
          with &nbsp;<tt><i>foo</i></tt>&nbsp; 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> &nbsp;<tt>url,location bar,field -focus</tt>&nbsp; 
     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 &nbsp;<tt>+foo</tt>&nbsp; to search for bugs where the <b>summary</b> contains &nbsp;<tt>foo</tt>&nbsp; as a <b>substring</b>.<br>
     Use &nbsp;<tt>#foo</tt>&nbsp; to search for bugs where the <b>summary</b> contains the <b>word</b> &nbsp;<tt>foo</tt>&nbsp; 
     <ul>
     <li> &nbsp;<tt>+brow</tt>&nbsp; does not find all bugs in the &nbsp;<tt>Browser</tt>&nbsp; product
     <li> &nbsp;<tt>#title</tt>&nbsp; does not find bugs bugs with &nbsp;<tt>titlebar</tt>&nbsp; or &nbsp;<tt>titled</tt>&nbsp; 
     </ul>
     Phrases with special chars (space, comma, +, -, #, ...) can be <b>quoted</b>:
     <ul>
     <li> &nbsp;<tt>"lock icon"</tt>&nbsp;
     </ul>
<p>
<li> <b>Open vs. Resolved Bugs</b>:<br>
     By default, only open (i.e. unresolved) bugs are shown.
     Use &nbsp;<tt>+DUP</tt>&nbsp; as first word in your query 
     to include duplicate bugs in your search, 
     &nbsp;<tt>FIXED</tt>&nbsp; to search for fixed bugs only,
     or &nbsp;<tt>ALL</tt>&nbsp; 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> &nbsp;<tt>+DUP,FIXED table border</tt>&nbsp;
     <li> &nbsp;<tt>ALL mouse wheel</tt>&nbsp;
     </ul>
<p>
<li> <b>Focus the Search with Products &amp; Components</b>:<br>
     To search for bugs in product "Foo Bar" only, add 
     &nbsp;<tt>:foo</tt>&nbsp; or &nbsp;<tt>:bar</tt>&nbsp; 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> &nbsp;<tt>12345</tt>&nbsp;
     </ul>
<li> A comma-separated list of bug numbers gives you a list of these bugs.
     <ul>
     <li> &nbsp;<tt>12345,23456,34567</tt>&nbsp;
     </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>