-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<!--
Contributor(s): Terry Weissman <terry@mozilla.org>
-->
+<head>
<TITLE>A Bug's Life Cycle</TITLE>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body>
<h1 ALIGN=CENTER>A Bug's Life Cycle</h1>
<hr>
<!-- hhmts start -->
-Last modified: Thu Aug 23 03:04:27 2000
+Last modified: Sun Apr 14 12:51:23 EST 2002
<!-- hhmts end -->
</body> </html>
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
-"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
-<meta http-equiv="content-type" content=
-"text/html;charset=iso-8859-1">
+<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<title>Bug Writing Guidelines</title>
</head>
<body>
</pre>
</blockquote>
+<p>
<b>Actual Results:</b> What the application did after performing
the above steps.
+</p>
<blockquote>
<pre>
segfault when the application finally crashes. Severe software
problems can manifest themselves in superficially trivial ways.
File them anyway.<br>
+</p>
</blockquote>
<p><b><a name="summary"></a>2. How and Why to Write Good Bug Summaries</b>
-<HTML><head>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
+<html><head>
<!--
The contents of this file are subject to the Mozilla Public
Contributor(s): Terry Weissman <terry@mozilla.org>
-->
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Understanding the UNCONFIRMED state, and other recent changes</title>
</head>
<body>
<h1>Understanding the UNCONFIRMED state, and other recent changes</h1>
+<p>
[This document is aimed primarily at people who have used Bugzilla
before the UNCONFIRMED state was implemented. It might be helpful for
newer users as well.]
+</p>
<p>
UNCONFIRMED that have been assigned to them, until they have been
confirmed in one way or another. (Engineers with more time will
hopefully glance over their UNCONFIRMED bugs regularly.)
+</p>
<p>
-
The <a href="bug_status.html">page describing bug fields</a> has been
updated to include UNCONFIRMED.
-<p>
+</p>
+<p>
There are two basic ways that a bug can become confirmed (and enter
the NEW) state.
+</p>
<ul>
<li> A user with the appropriate permissions (see below for more on
permissions) decides that the bug is a valid one, and confirms
it. We hope to gather a small army of responsible volunteers
- to regularly go through bugs for us.
- <li> The bug gathers a certain number of votes. <B>Any</B> valid Bugzilla user may vote for
+ to regularly go through bugs for us.</li>
+ <li> The bug gathers a certain number of votes. <b>Any</b> valid Bugzilla user may vote for
bugs (each user gets a certain number of bugs); any UNCONFIRMED bug which
-gets enough votes becomes automatically confirmed, and enters the NEW state.
+gets enough votes becomes automatically confirmed, and enters the NEW state.</li>
</ul>
+<p>
One implication of this is that it is worth your time to search the
bug system for duplicates of your bug to vote on them, before
submitting your own bug. If we can spread around knowledge of this
fact, it ought to help cut down the number of duplicate bugs in the
system.
+</p>
<h2>Permissions.</h2>
+<p>
Users now have a certain set of permissions. To see your permissions,
check out the
<a href="userprefs.cgi?bank=permissions">user preferences</a> page.
+</p>
<p>
-
If you have the "Can confirm a bug" permission, then you will be able
to move UNCONFIRMED bugs into the NEW state.
+</p>
<p>
-
If you have the "Can edit all aspects of any bug" permission, then you
can tweak anything about any bug. If not, you may only edit those
bugs that you have submitted, or that you have assigned to you (or
qa-assigned to you). However, anyone may add a comment to any bug.
+</p>
<p>
-
Some people (initially, the initial owners and initial qa-contacts for
components in the system) have the ability to give the above two
permissions to other people. So, if you really feel that you ought to
have one of these permissions, a good person to ask (via private
email, please!) is the person who is assigned a relevant bug.
+</p>
<h2>Other details.</h2>
+<p>
An initial stab was taken to decide who would be given which of the
above permissions. This was determined by some simple heurstics of
who was assigned bugs, and who the default owners of bugs were, and a
have been interesting and valid. Inevitably, we have failed to give
someone the permissions they deserve. Please don't take it
personally; just bear with us as we shake out the new system.
+</p>
<p>
-
-
People with one of the two bits above can easily confirm their own
bugs, so bugs they submit will actually start out in the NEW state.
They can override this when submitting a bug.
+</p>
<p>
-
People can ACCEPT or RESOLVE a bug assigned to them, even if they
aren't allowed to confirm it. However, the system remembers, and if
the bug gets REOPENED or reassigned to someone else, it will revert
back to the UNCONFIRMED state. If the bug has ever been confirmed,
then REOPENing or reassigning will cause it to go to the NEW or
REOPENED state.
+</p>
<p>
-
Note that only some products support the UNCONFIRMED state. In other
products, all new bugs will automatically start in the NEW state.
+</p>
<h2>Things still to be done.</h2>
+<p>
There probably ought to be a way to get a bug back into the
UNCONFIRMED state, but there isn't yet.
+</p>
<p>
-
If a person has submitted several bugs that get confirmed, then this
is probably a person who understands the system well, and deserves the
"Can confirm a bug" permission. This kind of person should be
detected and promoted automatically.
+</p>
<p>
-
There should also be a way to automatically promote people to get the
"Can edit all aspects of any bug" permission.
+</p>
<p>
-
The "enter a new bug" page needs to be revamped with easy ways for new
people to educate themselves on the benefit of searching for a bug
like the one they're about to submit and voting on it, rather than
adding a new useless duplicate.
+</p>
<hr>
+<p>
<!-- hhmts start -->
-Last modified: Wed Feb 16 21:04:56 2000
+Last modified: Sun Apr 14 12:55:14 EST 2002
<!-- hhmts end -->
+</p>
</body> </html>
DefParam("mybugstemplate",
"This is the URL to use to bring up a simple 'all of my bugs' list for a user. %userid% will get replaced with the login name of a user.",
"t",
- "buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=%userid%&emailtype1=exact&emailassigned_to1=1&emailreporter1=1");
+ "buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=%userid%&emailtype1=exact&emailassigned_to1=1&emailreporter1=1");
my $num = $4;
$item = value_quote($item); # Not really necessary, since we know
# there's no special chars in it.
- $item = qq{<A HREF="attachment.cgi?id=$num&action=view">$item</A>};
+ $item = qq{<a href="attachment.cgi?id=$num&action=view">$item</a>};
$things[$count++] = $item;
}
while ($text =~ s/\*\*\* This bug has been marked as a duplicate of (\d+) \*\*\*/"##$count##"/ei) {
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
<!--
The contents of this file are subject to the Mozilla Public
Contributor(s): Terry Weissman <terry@mozilla.org>
-->
+<head>
<TITLE>Clue</TITLE>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head><body>
<H1>A Clue</H1>
This form will allow you to call up a subset of the bug list.
You should be able to add the URL of the resulting list to
<P>
For example, if you wanted to see all bugs reported against the X platform
and assigned to jwz, you could ask for all bugs assign to jwz, then
-edit the URL in the "Location" box, adding the clause "&rep_platform=X-Windows"
+edit the URL in the "Location" box, adding the clause "&rep_platform=X-Windows"
to the URL.
<P>
Here is a list of some of the field names you could use for additional
seems to cache results of a .cgi. You'll sometimes need to press CONTROL-R to reload
the screen to see an update.
-</html>
+</body></html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html> <head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Help on searching by email address.</title>
</head>
<body>
<h1>Help on searching by email address.</h1>
+<p>
This used to be simpler, but not very powerful. Now it's really
powerful and useful, but it may not be obvious how to use it...
+</p>
<p>
-
To search for bugs associated with an email address:
+</p>
<ul>
- <li> Type a portion of an email address into the text field.
+ <li> Type a portion of an email address into the text field.</li>
<li> Select which fields of the bug you expect that address to be in
- the bugs you're looking for.
+ the bugs you're looking for.</li>
</ul>
<p>
-
You can look for up to two different email addresses; if you specify
both, then only bugs which match both will show up. This is useful to
find bugs that were, for example, created by Ralph and assigned to
Fred.
+</p>
<p>
-
You can also use the drop down menus to specify whether you want to
match addresses by doing a substring match, by using regular
expressions, or by exactly matching a fully specified email address.
-
-
+</p>
</body> </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML>
+<head>
<!--
The contents of this file are subject to the Mozilla Public
<TITLE>How to Mail to bugzilla</TITLE>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+</head>
+<body>
<H1>THIS DOESN'T WORK RIGHT NOW. Coming someday.</H1>
.
</PRE>
+
+</body></html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html> <head>
<title>No target milestones</title>
</head>
<body>
<h1>No target milestones.</h1>
+<p>
No target milestones have been defined for this product. You can set
the Target Milestone field to things, but there is not currently any
agreed definition of what the milestones are.
+</p>
+
+</body>
+</html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Bugzilla QuickSearch</title>
</head>
<body bgcolor="#ffffff">
+<p>
<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>
-<p>
-<script src="localconfig.js"></script>
-<script src="quicksearch.js"></script>
+<script src="localconfig.js" type="text/javascript"></script>
+<script src="quicksearch.js" type="text/javascript"></script>
<h1>Bugzilla QuickSearch</h1>
+<p>
Type in one or more words (or word fragments) to search for:
+</p>
<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><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>
+<script type="text/javascript">
<!--
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.
+ and <tt>TABLE</tt> are all the same.</li>
</ul>
+</li>
<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>.
+ <tt>localization</tt>.</li>
<li> Use <tt>bookmark</tt> instead of <tt>bookmarks</tt> or
- <tt>bookmarking</tt>.
+ <tt>bookmarking</tt>.</li>
</ul>
+</li>
</ul>
-<a name="features"/>
-<h2>Features</h2>
+<h2><a name="features">Features</a></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
+ with <tt><i>foo</i></tt> in the summary.</li>
+ <li> <b>AND</b>: Space-separated words are treated as a conjunction.</li>
+ <li> <b>OR</b>: 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
- <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>
+ (<tt>url</tt> OR <tt>location</tt>) AND (<tt>bar</tt> OR <tt>field</tt>) AND (NOT <tt>focus</tt>)
+<p>
+</li>
+<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>
+ <li> <tt>+brow</tt> does not find all bugs in the <tt>Browser</tt> product</li>
+ <li> <tt>#title</tt> does not find bugs bugs with <tt>titlebar</tt> or <tt>titled</tt> </li>
</ul>
Phrases with special chars (space, comma, +, -, #, ...) can be <b>quoted</b>:
<ul>
- <li> <tt>"lock icon"</tt>
+ <li> <tt>"lock icon"</tt> </li>
</ul>
<p>
+</li>
<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
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>
+ <li> <tt>+DUP,FIXED table border</tt> </li>
+ <li> <tt>ALL mouse wheel</tt> </li>
</ul>
-<p>
+<p></li>
<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
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 <b>lookup</b> a bug by its number.
<ul>
- <li> <tt>12345</tt>
+ <li> <tt>12345</tt> </li>
</ul>
+</li>
<li> A comma-separated list of bug numbers gives you a list of these bugs.
<ul>
- <li> <tt>12345,23456,34567</tt>
+ <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>
+</p>
<!--
<small>For further details, see
<a href="http://bugzilla.mozilla.org/show_bug.cgi?id=61561">Bug 61561</a> and
-->
<hr>
+<p>
Use the powerful
<a href="query.cgi">Bugzilla Query Form</a>
for advanced queries.
+</p>
</body>
</html>
-
-
-
-
-
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
+ <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Bugzilla QuickSearch (for Hackers)</title>
</head>
<body bgcolor="#ffffff">
-<script src="localconfig.js"></script>
-<script src="quicksearch.js"></script>
+<script src="localconfig.js" type="text/javascript"></script>
+<script src="quicksearch.js" type="text/javascript"></script>
<h1>Bugzilla QuickSearch (for Hackers)</h1>
+<p>
Type in one or more words (or word fragments) to search for:
+</p>
<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" name="run" value="Search"/></td>
- <td align=left><input type="button" name="load" value="Load Query"
- onclick="LoadQuery(f.id.value);" />
+ <td><input type="text" size="40" name="id"></td>
+ <td align="left"><input type="submit" name="run" value="Search"></td>
+ <td align="left"><input type="button" name="load" value="Load Query"
+ onclick="LoadQuery(f.id.value);">
</td>
</tr>
</table>
</form>
-<script>
+<script type="text/javascript">
<!--
document.forms['f'].id.focus();
//-->
By default, the following fields are relevant: 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>
<p>
The generic format for a ``word'' is
<tt>field1,...,fieldN:value1,...,valueM</tt> .
the prefix (roughly) defaults to <tt>summary,keywords,product,component,statuswhiteboard:</tt> as noted above.
You can use <tt>-<i>word</i></tt> to express the logical negation
of <tt><i>word</i></tt>.
+</p>
<p>
Here is a complete listing of available fields (the Shortcut column is just
for access speed):
-<p>
+</p>
-<table border=1>
+<table border="1">
<thead>
<tr>
<td><b>Searched by default</b></td>
<tr>
<td> </td>
- <td rowspan=2><tt><nobr>UNCO,NEW,...,CLOS,</nobr><br><nobr>FIX,DUP,...</nobr> <i><nobr>(as first word)</nobr></i></tt></td>
+ <td rowspan="2"><tt>UNCO,NEW,...,CLOS,<br>FIX,DUP,...<i>(as first word)</i></tt></td>
<td><tt>status</tt></td>
<td> </td>
<td><a href="bug_status.html">Status</a>
<tr>
<td><i>yes</i></td>
- <td rowspan=2><b>:</b><i>area</i></td>
+ <td rowspan="2"><b>:</b><i>area</i></td>
<td><tt>product</tt></td>
<td><tt>prod</tt></td>
<td>Product (enum)</td>
<p>
Examples for some useful abbreviations:
-<p>
-<table border=1>
+</p>
+<table border="1">
<thead>
<tr>
<td><b>Syntax</b></td>
</tr>
<tr>
<td><tt>blo,cri,maj</tt></td>
- <td><i>severe bugs</td>
+ <td><i>severe bugs</i></td>
</tr>
<tr>
<td><tt>enh</tt></td>
<td><b>priority:</b><i>level</i></td>
</tr>
<tr>
- <td><tt>p1<tt></td>
+ <td><tt>p1</tt></td>
<td><i>very high-priority bugs</i></td>
</tr>
<tr>
<td><tt>p1-2</tt></td>
- <td><i>high-priority bugs</td>
+ <td><i>high-priority bugs</i></td>
</tr>
<tr>
<td><b>@</b><i>owner</i></td>
More information can be found in the
<a href="quicksearch.html#features">"Features"</a> section
on the <a href="quicksearch.html">introductory page</a>.
+</p>
</body>
</html>
print <<FIN;
<center>
<h1>Welcome to the Bugzilla Query Kitchen</h1>
+</center>
<form method=get action=reports.cgi>
<table border=1 cellpadding=5>
<tr>
<b>E-mail address:</b>
</td>
<td>
- <input size="35" name="login" />
+ <input size="35" name="login">
[% Param('emailsuffix') FILTER html %]
</td>
</tr>
<b>Real name:</b>
</td>
<td>
- <input size="35" name="realname" />
+ <input size="35" name="realname">
</td>
</tr>
</table>
- <br />
- <input type="submit" value="Create Account" />
+ <br>
+ <input type="submit" value="Create Account">
</form>
[% INCLUDE global/footer %]
<tr>
<td valign="top">
[% IF attachment.isobsolete %]
- <strike><a href="attachment.cgi?id=[% attachment.attachid %]&action=view">[% attachment.description FILTER html %]</a></strike>
+ <strike><a href="attachment.cgi?id=[% attachment.attachid %]&action=view">[% attachment.description FILTER html %]</a></strike>
[% ELSE %]
- <a href="attachment.cgi?id=[% attachment.attachid %]&action=view">[% attachment.description FILTER html %]</a>
+ <a href="attachment.cgi?id=[% attachment.attachid %]&action=view">[% attachment.description FILTER html %]</a>
[% END %]
</td>
<td valign="top">
[% IF attachment.canedit %]
- <a href="attachment.cgi?id=[% attachment.attachid %]&action=edit">Edit</a>
+ <a href="attachment.cgi?id=[% attachment.attachid %]&action=edit">Edit</a>
[% ELSE %]
None
[% END %]
<tr>
<td colspan="4">
- <a href="attachment.cgi?bugid=[% bugid %]&action=enter">Create a New Attachment</a> (proposed patch, testcase, etc.)
+ <a href="attachment.cgi?bugid=[% bugid %]&action=enter">Create a New Attachment</a> (proposed patch, testcase, etc.)
</td>
<td colspan="1">
- <a href="attachment.cgi?bugid=[% bugid %]&action=viewall">View All</a>
+ <a href="attachment.cgi?bugid=[% bugid %]&action=viewall">View All</a>
</td>
</tr>
</table>
<tr align="left">
<th colspan="[% splitheader ? 2 : 1 %]">
- <a href="buglist.cgi?[% urlquerypart %]&order=bugs.bug_id">ID</a>
+ <a href="buglist.cgi?[% urlquerypart %]&order=bugs.bug_id">ID</a>
</th>
[% IF splitheader %]
[% BLOCK columnheader %]
<th colspan="[% splitheader ? 2 : 1 %]">
- <a href="buglist.cgi?[% urlquerypart %]&order=
+ <a href="buglist.cgi?[% urlquerypart %]&order=
[% column.name FILTER uri html %]
[% ",$order" FILTER uri html IF order %]">
[%- abbrev.$id.title || column.title -%]</a>
<table cellspacing="2" cellpadding="0" border="0">
<tr>
- <td><br /></td>
+ <td><br></td>
</tr>
<tr>
</tr>
<tr>
- <td><br /></td>
+ <td><br></td>
</tr>
<tr>
<td colspan="3">
<textarea wrap="hard" name="comment" rows="10" cols="80">
[% comment FILTER html %]</textarea>
- <br />
+ <br>
</td>
</tr>
<td></td>
<td colspan="3">
[% IF group.size %]
- <br />
+ <br>
<strong>
Only users in the selected groups can view this bug:
</strong>
- <br />
+ <br>
<font size="-1">
(Leave all boxes unchecked to make this a public bug.)
</font>
- <br />
- <br />
+ <br>
+ <br>
<!-- Checkboxes -->
[% FOREACH g = group %]
<input type="checkbox" name="bit-[% g.bit %]" value="1"
[% " checked=\"checked\"" IF g.checked %] />[% g.description %]<br />
[% END %]
- <br />
+ <br>
[% END %]
</td>
</tr>
<tr>
<td></td>
<td colspan="3">
- <br />
+ <br>
We've made a guess at your operating system and platform.
Please check them and, if we got it wrong, email
[% Param('maintainer') %].
[% END %]
</table>
- <input type="hidden" name="form_name" value="enter_bug" />
+ <input type="hidden" name="form_name" value="enter_bug">
</form>
[% INCLUDE global/footer %]
<script type="text/javascript" language="JavaScript" src="localconfig.js"></script>
<script type="text/javascript" language="JavaScript" src="quicksearch.js"></script>
-<script>
+<script type="text/javascript">
<!--
document.forms['f'].id.focus();
//-->
</tr>
[% END %]
-</table>
+[% IF keywords.size > 0 %]
+ </table>
+[% END %]
[% IF caneditkeywords %]
<p>
Only email me reports of changes made by other people
<input type="checkbox" name="ExcludeSelf" value="on"
[% " checked" IF excludeself %]>
- <br />
+ <br>
</td>
</tr>
</table>
<hr />
<b>Field/recipient specific options:</b>
-<br />
-<br />
+<br>
+<br>
<table width="100%" border="1">
[% END %]
</table>
-<br />
+<br>
[% ELSE %]
<tr>
<td colspan="4">
- <br />
+ <br>
If you create remembered queries using the
<a href="query.cgi">query page</a>,
you can then come to this page and choose to have some of them
appear in the footer of each Bugzilla page.
- <br />
- <br />
+ <br>
+ <br>
</td>
</tr>
[% END %]
</select>
</td>
<td>
- <input name="short_desc" size="40" value="[% default.short_desc.0 FILTER html %]" />
+ <input name="short_desc" size="40" value="[% default.short_desc.0 FILTER html %]">
</td>
<td>
- <input type="submit" value="Search" />
+ <input type="submit" value="Search">
</td>
</tr>
</select>
</td>
<td><input name="[% field.name %]" size="40" value="
- [% default.${field.name}.0 FILTER html %]" />
+ [% default.${field.name}.0 FILTER html %]">
</td>
<td></td>
</tr>
</select>
</td>
<td>
- <input name="keywords" size="40" value="[% default.keywords.0 FILTER html %]" />
+ <input name="keywords" size="40" value="[% default.keywords.0 FILTER html %]">
</td>
</tr>
[% END %]
<td>
<input type="checkbox" name="emailassigned_to[% n %]"
id="emailassigned_to[% n %]" value="1"
- [% " checked" IF default.emailassigned_to.$n %] />
+ [% " checked" IF default.emailassigned_to.$n %]>
<label for="emailassigned_to[% n %]">
bug owner
</label>
<td>
<input type="checkbox" name="emailreporter[% n %]"
id="emailreporter[% n %]" value="1"
- [% " checked" IF default.emailreporter.$n %] />
+ [% " checked" IF default.emailreporter.$n %]>
<label for="emailreporter[% n %]">
reporter
</label>
<td>
<input type="checkbox" name="emailqa_contact[% n %]"
id="emailqa_contact[% n %]" value="1"
- [% " checked" IF default.emailqa_contact.$n %] />
+ [% " checked" IF default.emailqa_contact.$n %]>
<label for="emailqa_contact[% n %]">
QA contact
</label>
<td>
<input type="checkbox" name="emailcc[% n %]"
id="emailcc[% n %]" value="1"
- [% " checked" IF default.emailcc.$n %] />
+ [% " checked" IF default.emailcc.$n %]>
<label for="emailcc[% n %]">
CC list member
</label>
<td>
<input type="checkbox" name="emaillongdesc[% n %]"
id="emaillongdesc[% n %]" value="1"
- [% " checked" IF default.emaillongdesc.$n %] />
+ [% " checked" IF default.emaillongdesc.$n %]>
<label for="emaillongdesc[% n %]">
commenter
</label>
</tr>
<tr>
<td>
- <input name="email[% n %]" size="20" value="[% default.email.$n FILTER html %]" />
+ <input name="email[% n %]" size="20" value="[% default.email.$n FILTER html %]">
</td>
</tr>
</table>
bugs numbered:
</td>
<td>
- <input type="text" name="bug_id" value="[% default.bug_id.0 FILTER html %]" size="20" />
+ <input type="text" name="bug_id" value="[% default.bug_id.0 FILTER html %]" size="20">
</td>
</tr>
<tr>
Only bugs with at least:
</td>
<td>
- <input name="votes" size="3" value="[% default.votes.0 FILTER html %]" /> votes
+ <input name="votes" size="3" value="[% default.votes.0 FILTER html %]"> votes
</td>
</tr>
</table>
<dl>
<dt>Only bugs changed in the last </dt>
- <dd><input name=changedin size=3 value="[% default.changedin.0 FILTER html %]" /> days</dd>
+ <dd><input name=changedin size=3 value="[% default.changedin.0 FILTER html %]"> days</dd>
</dl>
<dl>
<dt>were changed between</dt>
<dd>
- <input name="chfieldfrom" size="10" value="[% default.chfieldfrom.0 FILTER html %]" />
- and <input name="chfieldto" size="10" value="[% default.chfieldto.0 FILTER html %]" />
- <br />(YYYY-MM-DD)
+ <input name="chfieldfrom" size="10" value="[% default.chfieldfrom.0 FILTER html %]">
+ and <input name="chfieldto" size="10" value="[% default.chfieldto.0 FILTER html %]">
+ <br>(YYYY-MM-DD)
</dd>
<dt>to this value: (optional)</dt>
<dd>
- <input name="chfieldvalue" size="20" value="[% default.chfieldvalue.0 FILTER html %]" />
+ <input name="chfieldvalue" size="20" value="[% default.chfieldvalue.0 FILTER html %]">
</dd>
</dl>
<td colspan="2">
[% IF NOT userid %]
- <input type="hidden" name="cmdtype" value="doit" />
+ <input type="hidden" name="cmdtype" value="doit">
[% ELSE %]
- <br />
- <input type="radio" name="cmdtype" value="doit" checked /> Run this query
- <br />
+ <br>
+ <input type="radio" name="cmdtype" value="doit" checked> Run this query
+ <br>
[% IF namedqueries.size > 0 %]
<p>
<table cellspacing="0" cellpadding="0">
<tr>
<td>
- <input type="radio" name="cmdtype" value="editnamed" />
+ <input type="radio" name="cmdtype" value="editnamed">
Load my remembered query:
</td>
<td rowspan="3">
</tr>
<tr>
<td>
- <input type="radio" name="cmdtype" value="runnamed" />
+ <input type="radio" name="cmdtype" value="runnamed">
Run my remembered query:
</td>
</tr>
<tr>
<td>
- <input type="radio" name="cmdtype" value="forgetnamed" />
+ <input type="radio" name="cmdtype" value="forgetnamed">
Forget my remembered query:
</td>
</tr>
</p>
[% END %]
- <input type="radio" name="cmdtype" value="asdefault" />
+ <input type="radio" name="cmdtype" value="asdefault">
Remember this as my default query
- <br />
- <input type="radio" name="cmdtype" value="asnamed" />
+ <br>
+ <input type="radio" name="cmdtype" value="asnamed">
Remember this query, and name it:
<input type="text" name="newqueryname">
- <br /> <input type="checkbox" name="tofooter" value="1" />
+ <br> <input type="checkbox" name="tofooter" value="1">
and put it in my page footer
- <br />
+ <br>
[% END %]
- <br />
+ <br>
<div>
Sort results by:
<select name="order">
[% END %]
</select>
- <input type="submit" value="Search" />
+ <input type="submit" value="Search">
[% IF userdefaultquery %]
<p>
<a href="query.cgi?nukedefaultquery=1">
</select>
<input name="[% "value${chartnum}-${rownum}-${colnum}" %]"
- value="[% col.value FILTER html %]" />
+ value="[% col.value FILTER html %]">
</td>
[% IF NOT col == row.last %]
<td>
[% newor = colnum + 1 %]
<input type="submit" value="Or"
- name="cmd-add[% "${chartnum}-${rownum}-${newor}" %]" [% $jsmagic %] />
+ name="cmd-add[% "${chartnum}-${rownum}-${newor}" %]" [% $jsmagic %]>
</td>
[% END %]
<td>
[% newand = rownum + 1; newchart = chartnum + 1 %]
<input type="submit" value="And"
- name="cmd-add[% "${chartnum}-${newand}-0" %]"[% $jsmagic %] />
+ name="cmd-add[% "${chartnum}-${newand}-0" %]"[% $jsmagic %]>
<input type="submit" value="Add another boolean chart"
- name="cmd-add[% newchart %]-0-0" [% $jsmagic %] />
+ name="cmd-add[% newchart %]-0-0" [% $jsmagic %]>
</td>
</tr>
[% operation.when %]
</td>
[% FOREACH change = operation.changes %]
- [% "<tr>" IF loop.index > 0 %]
+ [% "</tr><tr>" IF loop.index > 0 %]
<td>
[% IF change.attachid %]
- <a href="attachment.cgi?id=[% change.attachid %]&action=view">
+ <a href="attachment.cgi?id=[% change.attachid %]&action=view">
Attachment #[% change.attachid %]</a>
[% END %]
[% change.field %]
[% END %]
</td>
- [% "</tr>" IF loop.index > 0 %]
[% END %]
</tr>
[% END %]
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<!--
The contents of this file are subject to the Mozilla Public
Contributor(s): Terry Weissman <terry@mozilla.org>
-->
<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>Bugzilla Voting</title>
</head>
<p>
To look at votes:
+</p>
<ul>
<li> Go to the query page. Do a normal query, but enter 1 in the
"At least ___ votes" field. This will show you items that
- match your query that have at least one vote.
+ match your query that have at least one vote.</li>
</ul>
-</p>
<p>
To vote for a bug:
+</p>
<ul>
- <li> Bring up the bug in question.
+ <li> Bring up the bug in question.</li>
<li> Click on the "Vote for this bug" link that appears just above
the "Additional Comments" field. (If no such link appears,
- then voting may not be allowed in this bug's product.)
+ then voting may not be allowed in this bug's product.)</li>
<li> Indicate how many votes you want to give this bug. This page
also displays how many votes you've given to other bugs, so you
- may rebalance your votes as necessary.
+ may rebalance your votes as necessary.</li>
</ul>
+<p>
You will automatically get email notifying you of any changes that
occur on bugs you vote for.
</p>
projects / thirdparty / bugzilla.git / commitdiff
