Bug 22198 - CLOSED status not documented
Summary: CLOSED status not documented
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General   
(Show other bugs)
Version: 2.8
Hardware: i386 Linux
medium
medium vote
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL: http://bugzilla.redhat.com/bugzilla/b...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-12-13 06:47 UTC by Stephen Rasku
Modified: 2007-04-18 16:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-12-13 10:43:29 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Stephen Rasku 2000-12-13 06:47:13 UTC
On the bug status documentation page, it doesn't document the CLOSED
status.  It should, as a minimum, explain who can close a bug (i.e. can an
external reporter close a bug) and under what circumstances you should
close a bug.

For mozilla, someone may resolve a bug I reported.  I then download the
latest version and test whether the bug has really been fixed.  If it has
been fixed, I mark it VERIFIED.  RH doesn't have a VERIFIED status. Is the
CLOSED status an equivalent?

Comment 1 David Lawrence 2000-12-13 15:29:19 UTC
Okay, I have added a description to the bug_status.cgi page to explain the
nature of the CLOSED status a little better. This is status has been debated
within Red Hat for some time now and is actually rarely used. I may end up doing
away with it entirely but until that time I have put a description of what it
could be used for on the help page.


Note You need to log in before you can comment on or make changes to this bug.