Bug 76020 - resolved/closed dichotomy is back
Summary: resolved/closed dichotomy is back
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 2.17
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: David Lawrence
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-15 21:15 UTC by Bill Nottingham
Modified: 2014-03-17 02:31 UTC (History)
2 users (show)

Fixed In Version: 2.18
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-05-01 20:53:49 UTC
Embargoed:

Attachments (Terms of Use)

Description Bill Nottingham 2002-10-15 21:15:58 UTC 
In our current bugzilla, there is only closed, not both 'resolved' and 'closed'.
Comment 1 David Lawrence 2002-10-16 19:40:15 UTC 
Fixed the behaviour to close a bug when resolving instead of RESOLVED. As for
RESOLVED being in the list of status to query against from query.cgi, this has
been like this for some time. Not a regression.
Comment 2 Aleksey Nogin 2002-12-13 20:00:43 UTC 
There are currently 720 bugs with status "RESOLVED".

Also, marking as a duplicate uses "RESOLVED DUPLICATE", not "CLOSED DUPLICATE".
Comment 3 Aleksey Nogin 2002-12-13 20:04:50 UTC 
P.S. Should all the bugs that existed prior to Bugzilla upgrade be changed to
"everconfirmed=1"? Otherwise we'll have these weird occurrences of "UNCONFIRMED"
status in reopened bugs, bugmail showing "everconfirmed" changing from 0 to 1
(for no good reason), etc.
Note You need to log in before you can comment on or make changes to this bug.