Bug 170213 - make static HTML files into page.cgi pages. This does votehelp.html…

editproducts.cgi

@@ -137,7 +137,7 @@ sub EmitFormElements ($$$$$$$$)
     print "  <TD><INPUT SIZE=5 MAXLENGTH=5 NAME=\"maxvotesperbug\" VALUE=\"$maxvotesperbug\"></TD>\n";
 
     print "</TR><TR>\n";
-    print "  <TH ALIGN=\"right\">Number of votes a bug in this product needs to automatically get out of the <A HREF=\"bug_status.html#status\">UNCONFIRMED</A> state:</TH>\n";
+    print "  <TH ALIGN=\"right\">Number of votes a bug in this product needs to automatically get out of the <A HREF=\"page.cgi?id=fields.html#status\">UNCONFIRMED</A> state:</TH>\n";
     print "  <TD><INPUT SIZE=5 MAXLENGTH=5 NAME=\"votestoconfirm\" VALUE=\"$votestoconfirm\"></TD>\n";
 }
 

quicksearchhack.html

@@ -79,7 +79,7 @@ for access speed):
   <td rowspan="2"><tt>UNCO,NEW,...,CLOS,<br>FIX,DUP,...<i>(as first word)</i></tt></td>
   <td><tt>status</tt></td>
   <td>&nbsp;</td>
-  <td><a href="bug_status.html">Status</a> 
+  <td><a href="page.cgi?id=fields.html#status">Status</a> 
       <i>("bug_status")</i>
   </td>
 </tr>
@@ -87,35 +87,35 @@ for access speed):
   <td>&nbsp;</td>
   <td><tt>resolution</tt></td>
   <td>&nbsp;</td>
-  <td><a href="bug_status.html">Resolution</a></td>
+  <td><a href="page.cgi?id=fields.html#resolution">Resolution</a></td>
 </tr>
 <tr>
   <td>&nbsp;</td>
   <td><i>as-is</i></td>
   <td><tt>platform</tt></td>
   <td>&nbsp;</td>
-  <td><a href="bug_status.html#rep_platform">Platform</a> <i>("rep_platform")</i></td>
+  <td><a href="page.cgi?id=fields.html#rep_platform">Platform</a> <i>("rep_platform")</i></td>
 </tr>
 <tr>
   <td>&nbsp;</td>
   <td>&nbsp;</td>
   <td><tt>os</tt></td>
   <td><tt>opsys</tt></td>
-  <td><a href="bug_status.html#op_sys">OS</a> <i>("op_sys")</i></td>
+  <td><a href="page.cgi?id=fields.html#op_sys">OS</a> <i>("op_sys")</i></td>
 </tr>
 <tr>
   <td>&nbsp;</td>
   <td><tt>p1,p2</tt> <i>or</i> <tt>p1-2</tt></td>
   <td><tt>priority</tt></td>
   <td><tt>pri</tt></td>
-  <td><a href="bug_status.html#priority">Priority</a></td>
+  <td><a href="page.cgi?id=fields.html#priority">Priority</a></td>
 </tr>
 <tr>
   <td>&nbsp;</td>
   <td><tt>blo,cri,...,enh</tt></td>
   <td><tt>severity</tt></td>
   <td><tt>sev</tt></td>
-  <td><a href="bug_status.html#severity">Severity</a> <i>("bug_severity")</i></td>
+  <td><a href="page.cgi?id=fields.html#bug_severity">Severity</a> <i>("bug_severity")</i></td>
 </tr>
 
 <!-- People: AssignedTo, Reporter, QA Contact, CC, Added comment -->
@@ -126,7 +126,7 @@ for access speed):
   <td><b>@</b><i>owner</i></td>
   <td><tt>assignedto</tt></td>
   <td><tt>assignee, owner</tt></td>
-  <td><a href="bug_status.html#assigned_to">Assignee</a> <i>("assigned_to")</i></td>
+  <td><a href="page.cgi?id=fields.html#assigned_to">Assignee</a> <i>("assigned_to")</i></td>
 </tr>
 <tr>
   <td>&nbsp;</td>

template/en/default/bug/create/create.html.tmpl

@@ -176,7 +176,7 @@ function set_assign_to() {
   <tr>
     <td align="right">
       <strong>
-        <a href="bug_status.html#assigned_to">Assign To</a>:
+        <a href="page.cgi?id=fields.html#assigned_to">Assign To</a>:
       </strong>
     </td>
     <td colspan="3">
@@ -333,7 +333,8 @@ function set_assign_to() {
   [% IF sel.description %]
   <td align="right">
     <strong>
-      <a href="bug_status.html#[% sel.name %]">[% sel.description %]</a>:
+      <a href="page.cgi?id=fields.html#[% sel.name %]">
+        [% sel.description %]</a>:
     </strong>
   </td>
   [% END %]

template/en/default/bug/create/user-message.html.tmpl

@@ -30,7 +30,8 @@
 
 [% PROCESS global/variables.none.tmpl %]
 
-Before reporting [% terms.abug %], please read the <a href="bugwritinghelp.html">
+Before reporting [% terms.abug %], please read the 
+<a href="page.cgi?id=bug-writing.html">
 [% terms.bug %] writing guidelines</a>, please look at the list of
 <a href="duplicates.cgi">most frequently reported [% terms.bugs %]</a>, and please
 <a href="query.cgi">search</a> for the [% terms.bug %].

template/en/default/bug/edit.html.tmpl

@@ -205,14 +205,14 @@
     <tr>
       <td align="right">
         <b>
-          <a href="bug_status.html">Status</a>:
+          <a href="page.cgi?id=fields.html#status">Status</a>:
         </b>
       </td>
       <td>[% bug.bug_status FILTER html %]</td>
       <td>&nbsp;</td>
 
       <td align="right">
-        <b><a href="bug_status.html#priority">Pr<u>i</u>ority</a>:</b>
+        <b><a href="page.cgi?id=fields.html#priority">Pr<u>i</u>ority</a>:</b>
       </td>
       [% PROCESS select selname => "priority" accesskey => "i" %]
     </tr>
@@ -220,7 +220,7 @@
     <tr>
       <td align="right">
         <b>
-          <a href="bug_status.html">Resolution</a>:
+          <a href="page.cgi?id=fields.html#resolution">Resolution</a>:
         </b>
       </td>
       <td>
@@ -232,7 +232,7 @@
       <td>&nbsp;</td>
 
       <td align="right">
-        <b><a href="bug_status.html#severity">S<u>e</u>verity</a>:</b>
+        <b><a href="page.cgi?id=fields.html#severity">S<u>e</u>verity</a>:</b>
       </td>
       [% PROCESS select selname = "bug_severity" accesskey => "e" %]
 
@@ -241,7 +241,7 @@
     <tr>
       <td align="right">
         <b>
-          <a href="bug_status.html#assigned_to">Assigned&nbsp;To</a>:
+          <a href="page.cgi?id=fields.html#assigned_to">Assigned&nbsp;To</a>:
         </b>
       </td>
       <td>[% bug.assigned_to.identity FILTER html %]</td>
@@ -428,7 +428,7 @@
   <table>
     <tr>
       <th>
-        <a href="votehelp.html">Votes</a>:
+        <a href="page.cgi?id=voting.html">Votes</a>:
       </th>
       <td>
         [% bug.votes %]&nbsp;&nbsp;&nbsp;

template/en/default/bug/knob.html.tmpl

@@ -59,7 +59,8 @@
       [% END %]
 
       <input type="radio" name="knob" value="resolve">
-      Resolve [% terms.bug %], changing <a href="bug_status.html">resolution</a> to
+      Resolve [% terms.bug %], changing 
+      <a href="page.cgi?id=fields.html#resolution">resolution</a> to
       <select name="resolution"
               onchange="document.changeform.knob[[% knum %]].checked=true">
       [% FOREACH r = bug.choices.resolution %]
@@ -78,7 +79,8 @@
       [% knum = knum + 1 %]
 
       <input type="radio" name="knob" value="reassign">
-      <a href="bug_status.html#assigned_to">Reassign</a> [% terms.bug %] to
+      <a href="page.cgi?id=fields.html#assigned_to">Reassign</a> 
+      [% terms.bug %] to
       <input name="assigned_to" size="32"
              onchange="if ((this.value != '[% bug.assigned_to.email FILTER js %]') &&
                             (this.value != '')) {

template/en/default/bug/votes/list-for-user.html.tmpl

@@ -141,7 +141,7 @@
 [% END %]
 
 <p>
-  <a href="votehelp.html">Help with voting</a>.
+  <a href="page.cgi?id=voting.html">Help with voting</a>.
 </p>
 
 [% PROCESS global/footer.html.tmpl %]

template/en/default/list/edit-multiple.html.tmpl

@@ -70,7 +70,7 @@
 
     <th>
       <label for="rep_platform">
-        <a href="bug_status.html#rep_platform">Platform</a>:
+        <a href="page.cgi?id=fields.html#rep_platform">Platform</a>:
       </label>
     </th>
     <td>
@@ -80,7 +80,7 @@
 
     <th>
       <label for="priority">
-        <a href="bug_status.html#priority">Priority</a>:
+        <a href="page.cgi?id=fields.html#priority">Priority</a>:
       </label>
     </th>
     <td>
@@ -99,7 +99,7 @@
 
     <th>
       <label for="bug_severity">
-        <a href="bug_status.html#severity">Severity</a>:
+        <a href="page.cgi?id=fields.html#severity">Severity</a>:
       </label>
     </th>
     <td>
@@ -266,7 +266,7 @@
   [% knum = knum + 1 %]
   <input id="knob-resolve" type="radio" name="knob" value="resolve">
   <label for="knob-resolve">
-    Resolve [% terms.bugs %], changing <a href="bug_status.html">resolution</a> to
+    Resolve [% terms.bugs %], changing <a href="page.cgi?id=fields.html#resolution">resolution</a> to
   </label>
   <select name="resolution" onchange="document.forms.changeform.knob[[% knum %]].checked=true">
     [% FOREACH resolution = resolutions %]
@@ -300,7 +300,7 @@
 
 [% knum = knum + 1 %]
 <input id="knob-reassign" type="radio" name="knob" value="reassign">
-<label for="knob-reassign"><a href="bug_status.html#assigned_to">
+<label for="knob-reassign"><a href="page.cgi?id=fields.html#assigned_to">
   Reassign</a> [% terms.bugs %] to
 </label>
 <input name="assigned_to"

template/en/default/pages/fields.html.tmpl

+[%# 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.
+  #
+  # The Initial Developer of the Original Code is Netscape Communications
+  # Corporation. Portions created by Netscape are
+  # Copyright (C) 1998 Netscape Communications Corporation. All
+  # Rights Reserved.
+  #
+  # Contributor(s): Terry Weissman <terry@mozilla.org>
+  #                 Gervase Markham <gerv@gerv.net>
+  #%]
+
+[% PROCESS global/variables.none.tmpl %]
+[% INCLUDE global/header.html.tmpl title = "A $terms.Bug's Life Cycle" %]
+
+<p>
+The <b>status</b> and <b>resolution</b> fields define and track the life
+cycle of a [% terms.bug %].  
+</p>
+
+<a name="status"></a>
+<a name="resolution"></a>
+
+<table border="1" cellpadding="4">
+  <tr align="center" valign="top">
+    <td width="50%">
+      <h1>STATUS</h1>
+    </td>
+
+    <td>
+      <h1>RESOLUTION</h1>
+    </td>
+  </tr>
+
+  <tr valign="top">
+    <td>The <b>status</b> field indicates the general health of a 
+    [% terms.bug %]. Only certain status transitions are allowed.</td>
+
+    <td>The <b>resolution</b> field indicates what happened to this
+    [% terms.bug %].</td>
+  </tr>
+
+  <tr valign="top">
+    <td>
+      <dl>
+        <dt><b>UNCONFIRMED</b></dt>
+
+        <dd>This [% terms.bug %] has recently been added to the database. 
+        Nobody has validated that this [% terms.bug %] is true. Users who have
+        the "canconfirm" permission set may confirm this [% terms.bug %], 
+        changing its state to NEW. Or, it may be directly resolved and marked 
+        RESOLVED.</dd>
+
+        <dt><b>NEW</b></dt>
+
+        <dd>This [% terms.bug %] has recently been added to the assignee's list 
+        of [% terms.bugs %] and must be processed. [% terms.Bugs %] in this 
+        state may be accepted, and become <b>ASSIGNED</b>, passed on to someone 
+        else, and remain <b>NEW</b>, or resolved and marked <b>RESOLVED</b>.
+        </dd>
+
+        <dt><b>ASSIGNED</b></dt>
+
+        <dd>This [% terms.bug %] is not yet resolved, but is assigned to the 
+        proper person. From here [% terms.bugs %] can be given to another 
+        person and become <b>NEW</b>, or resolved and become <b>RESOLVED</b>.
+        </dd>
+
+        <dt><b>REOPENED</b></dt>
+
+        <dd>This [% terms.bug %] was once resolved, but the resolution was 
+        deemed incorrect. For example, a <b>WORKSFORME</b> [% terms.bug %] is 
+        <b>REOPENED</b> when more information shows up and the [% terms.bug %]
+        is now reproducible. From here [% terms.bugs %] are either marked 
+        <b>ASSIGNED</b> or <b>RESOLVED</b>.</dd>
+      </dl>
+    </td>
+
+    <td>
+      <dl>
+        <dd>No resolution yet. All [% terms.bugs %] which are in one of 
+        these "open" states have the resolution set to blank. All 
+        other [% terms.bugs %] will be marked with one of the following 
+        resolutions.</dd>
+      </dl>
+    </td>
+  </tr>
+
+  <tr valign="top">
+    <td>
+      <dl>
+        <dt><b>RESOLVED</b></dt>
+
+        <dd>A resolution has been taken, and it is awaiting verification by
+        QA. From here [% terms.bugs %] are either re-opened and become 
+        <b>REOPENED</b>, are marked <b>VERIFIED</b>, or are closed for good 
+        and marked <b>CLOSED</b>.</dd>
+
+        <dt><b>VERIFIED</b></dt>
+
+        <dd>QA has looked at the [% terms.bug %] and the resolution and 
+        agrees that the appropriate resolution has been taken. [% terms.Bugs %]
+        remain in this state until the product they were reported against 
+        actually ships, at which point they become <b>CLOSED</b>.</dd>
+
+        <dt><b>CLOSED</b></dt>
+
+        <dd>The [% terms.bug %] is considered dead, the resolution is correct. 
+        Any zombie [% terms.bugs %] who choose to walk the earth again must 
+        do so by becoming <b>REOPENED</b>.</dd>
+      </dl>
+    </td>
+
+    <td>
+      <dl>
+        <dt><b>FIXED</b></dt>
+
+        <dd>A fix for this [% terms.bug %] is checked into the tree and 
+        tested.</dd>
+
+        <dt><b>INVALID</b></dt>
+
+        <dd>The problem described is not a [% terms.bug %]</dd>
+
+        <dt><b>WONTFIX</b></dt>
+
+        <dd>The problem described is a [% terms.bug %] which will never be 
+        fixed.</dd>
+
+        <dt><b>DUPLICATE</b></dt>
+
+        <dd>The problem is a duplicate of an existing [% terms.bug %]. Marking 
+        a [% terms.bug %] duplicate requires the [% terms.bug %]# of the 
+        duplicating [% terms.bug %] and will at least put that [% terms.bug %] 
+        number in the description field.</dd>
+
+        <dt><b>WORKSFORME</b></dt>
+
+        <dd>All attempts at reproducing this [% terms.bug %] were futile, 
+        reading the code produces no clues as to why this behavior would occur. 
+        If more information appears later, please re-assign 
+        the [% terms.bug %], for now, file it.</dd>
+
+        <dt><b>MOVED</b></dt>
+
+        <dd>The problem was specific to a related product 
+        whose [% terms.bugs %] are tracked in another [% terms.bug %] database. 
+        The [% terms.bug %] has been moved to that database.</dd>
+      </dl>
+    </td>
+  </tr>
+</table>
+
+<h2><a name="bug_severity">Severity</a></h2>
+This field describes the impact of a [% terms.bug %]. 
+
+<table>
+  <tr>
+    <th>Blocker</th>
+
+    <td>Blocks development and/or testing work</td>
+  </tr>
+
+  <tr>
+    <th>Critical</th>
+
+    <td>crashes, loss of data, severe memory leak</td>
+  </tr>
+
+  <tr>
+    <th>Major</th>
+
+    <td>major loss of function</td>
+  </tr>
+
+  <tr>
+    <th>Minor</th>
+
+    <td>minor loss of function, or other problem where easy
+    workaround is present</td>
+  </tr>
+
+  <tr>
+    <th>Trivial</th>
+
+    <td>cosmetic problem like misspelled words or misaligned
+    text</td>
+  </tr>
+
+  <tr>
+    <th>Enhancement</th>
+
+    <td>Request for enhancement</td>
+</table>
+
+<h2><a name="priority">Priority</a></h2>
+This field describes the importance and order in which a [% terms.bug %]
+should be fixed. This field is utilized by the
+programmers/engineers to prioritize their work to be done. The
+available priorities range from <b>P1</b> (most important) to 
+<b>P5</b> (least important.) 
+
+
+<h2><a name="rep_platform">Platform</a></h2>
+This is the hardware platform against which the [% terms.bug %] was
+reported. Legal platforms include: 
+
+<ul>
+  <li>All (happens on all platforms; cross-platform [% terms.bug %])</li>
+
+  <li>Macintosh</li>
+
+  <li>PC</li>
+
+  <li>Sun</li>
+
+  <li>HP</li>
+</ul>
+<b>Note:</b> When searching, selecting the option "All" does not 
+select [% terms.bugs %]
+assigned against any platform. It merely selects [% terms.bugs %] that are
+marked as occurring on all platforms, i.e. are designated "All". 
+
+<h2><a name="op_sys">Operating System</a></h2>
+This is the operating system against which the [% terms.bug %] was
+reported. Legal operating systems include: 
+
+<ul>
+  <li>All (happens on all operating systems; cross-platform
+  [% terms.bug %])</li>
+
+  <li>Windows 95</li>
+
+  <li>Mac System 8.0</li>
+
+  <li>Linux</li>
+</ul>
+Sometimes the operating system implies the platform, but not
+always. For example, Linux can run on PC and Macintosh and
+others. 
+
+<h2><a name="assigned_to">Assigned To</a></h2>
+
+<p>
+This is the person in charge of resolving the [% terms.bug %]. Every time
+this field changes, the status changes to <b>NEW</b> to make it
+easy to see which new [% terms.bugs %] have appeared on a person's list.</p>
+
+<p>
+The default status for queries is set to NEW, ASSIGNED and
+REOPENED. When searching for [% terms.bugs %] that have been resolved or
+verified, remember to set the status field appropriately. 
+</p>
+
+[% INCLUDE global/footer.html.tmpl %]

template/en/default/pages/voting.html.tmpl

+[%# 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.
+  #
+  # The Initial Developer of the Original Code is Netscape Communications
+  # Corporation. Portions created by Netscape are
+  # Copyright (C) 1998 Netscape Communications Corporation. All
+  # Rights Reserved.
+  #
+  # Contributor(s): Terry Weissman <terry@mozilla.org>
+  #                 Gervase Markham <gerv@gerv.net>
+  #%]
+
+[% PROCESS global/variables.none.tmpl %]
+[% INCLUDE global/header.html.tmpl title = "Voting" %]
+
+<p>[% terms.Bugzilla %] has a "voting" feature. Each product allows users to 
+have a certain number of votes. (Some products may not allow any, which means 
+you can't vote on things in that product at all.) With your vote, you indicate
+which [% terms.bugs %] you think are the most important to be fixed.</p>
+
+<p>Depending on how the administrator has configured the relevant product,
+you may be able to vote for the same [% terms.bug %] more than one time. But 
+remember, you only have so many votes to use in total! So, you can either vote 
+a little for many [% terms.bugs %], or vote a lot for a few [% terms.bugs %].
+</p>
+
+<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.</li>
+</ul>
+
+<p>To vote for a [% terms.bug %]:</p>
+
+<ul>
+  <li>Bring up the [% terms.bug %] in question.</li>
+
+  <li>Click on the "Vote for this [% terms.bug %]" link that appears just 
+  above the "Additional Comments" field. (If no such link appears, then voting 
+  may not be allowed in this [% terms.bug %]'s product.)</li>
+
+  <li>Indicate how many votes you want to give this [% terms.bug %]. This page 
+  also displays how many votes you've given to other [% terms.bugs %], so you 
+  may rebalance your votes as necessary.</li>
+</ul>
+
+<p>You will automatically get email notifying you of any changes that occur
+on [% terms.bugs %] you vote for.</p>
+
+<p>You may review your votes at any time by clicking on the "<a href=
+"votes.cgi?action=show_user">My Votes</a>" link in the page footer.</p>
+
+[% INCLUDE global/footer.html.tmpl %]