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
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
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
|
[%# 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 %]
|
