2 @section States of Problem Reports
4 @cindex life-cycle of a Problem Report
5 @cindex states of Problem Reports
6 @cindex Problem Report states
7 @cindex automatic notification
9 Each PR goes through a defined series of states between origination and
10 closure. The originator of a PR receives notification automatically of
13 Unless your site has customized states (see @pxref{states
14 file,,,gnats}), @sc{gnats} uses these states:
17 @cindex @emph{open} state
18 @cindex initial state (@dfn{open})
19 @cindex state---@dfn{open}
21 The initial state of a Problem Report. This means the PR has been filed
22 and the responsible person(s) notified.
24 @cindex @emph{analyzed} state
25 @cindex state---@dfn{analyzed}
27 The responsible person has analyzed the problem. The analysis should
28 contain a preliminary evaluation of the problem and an estimate of the
29 amount of time and resources necessary to solve the problem. It should
30 also suggest possible workarounds.
32 @cindex @emph{feedback} state
33 @cindex state---@dfn{feedback}
35 The problem has been solved, and the originator has been given a patch
36 or other fix. The PR remains in this state until the originator
37 acknowledges that the solution works.
39 @cindex @emph{closed} state
40 @cindex state---@dfn{closed}
41 @cindex final state (@dfn{closed})
43 A Problem Report is closed (``the bug stops here'') only when any
44 changes have been integrated, documented, and tested, and the submitter
45 has confirmed the solution.
47 @cindex @emph{suspended} state
48 @cindex state---@dfn{suspended}
50 Work on the problem has been postponed. This happens if a timely
51 solution is not possible or is not cost-effective at the present time.
52 The PR continues to exist, though a solution is not being actively
53 sought. If the problem cannot be solved at all, it should be closed
54 rather than suspended.