diff options
| author | cyeh%bluemartini.com <> | 2000-08-29 02:48:56 +0200 |
|---|---|---|
| committer | cyeh%bluemartini.com <> | 2000-08-29 02:48:56 +0200 |
| commit | f8fc58cc98b1a13d8264c838b8e0accd5b1d6e96 (patch) | |
| tree | b3486df842c5fe536a90ea2bbfdee8f0817ae7ac /bug_status.html | |
| parent | e6fae1e06eb79da44701ae6fea2e8b296c92e75e (diff) | |
| download | bugzilla-f8fc58cc98b1a13d8264c838b8e0accd5b1d6e96.tar.gz bugzilla-f8fc58cc98b1a13d8264c838b8e0accd5b1d6e96.tar.xz | |
fix for 47790 : A bug to track which bugs Zach's bugzilla patch resolves.
patches by zach@zachlipton.com. Thanks!
Diffstat (limited to 'bug_status.html')
| -rwxr-xr-x | bug_status.html | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/bug_status.html b/bug_status.html index 18d64d3ad..2b052786d 100755 --- a/bug_status.html +++ b/bug_status.html @@ -1,3 +1,4 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <!-- @@ -30,13 +31,12 @@ The <B>status</B> and <B>resolution</B> field define and track the life cycle of a bug. -<a name="status"> +<a name="status"></a> <p> -</a> <TABLE BORDER=1 CELLPADDING=4> <TR ALIGN=CENTER VALIGN=TOP> -<TD WIDTH=50%><H1>STATUS</H1> <TD><H1>RESOLUTION</H1> +<TD WIDTH="50%"><H1>STATUS</H1> <TD><H1>RESOLUTION</H1> <TR VALIGN=TOP> <TD>The <B>status</B> field indicates the general health of a bug. Only @@ -120,7 +120,7 @@ certain status transitions are allowed. <H1>Other Fields</H1> <table border=1 cellpadding=4><tr><td> -<a name="severity"><h2>Severity</h2></a> +<h2><a name="severity">Severity</a></h2> This field describes the impact of a bug. @@ -132,13 +132,13 @@ This field describes the impact of a bug. <tr><th>Critical</th><td>crashes, loss of data, severe memory leak <tr><th>Major</th><td>major loss of function <tr><th>Minor</th><td>minor loss of function, or other problem where easy workaround is present -<tr><th>Trivial</th><td>cosmetic problem like misspelt words or misaligned text +<tr><th>Trivial</th><td>cosmetic problem like misspelled words or misaligned text <tr><th>Enhancement</th><td>Request for enhancement </table> </td><td> -<a name="priority"><h2>Priority</h2></a> +<h2><a name="priority">Priority</a></h2> This field describes the importance and order in which a bug should be fixed. This field is utilized by the programmers/engineers to @@ -156,7 +156,7 @@ prioritized their work to be done. The available priorities are: </table> </tr></table> -<a name="rep_platform"><h2>Platform</h2></a> +<h2><a name="rep_platform">Platform</a></h2> This is the hardware platform against which the bug was reported. Legal platforms include: @@ -171,7 +171,7 @@ platforms include: <b>Note:</b> Selecting the option "All" does not select bugs assigned against all platforms. It merely selects bugs that <b>occur</b> on all platforms. -<a name="op_sys"><h2>Operating System</h2></a> +<h2><a name="op_sys">Operating System</a></h2> This is the operating system against which the bug was reported. Legal operating systems include: @@ -185,7 +185,7 @@ operating systems include: Note that the operating system implies the platform, but not always. For example, Linux can run on PC and Macintosh and others. -<a name="assigned_to"><h2>Assigned To</h2></a> +<h2><a name="assigned_to">Assigned To</a></h2> This is the person in charge of resolving the bug. Every time this field changes, the status changes to <B>NEW</B> to make it easy to see |