On other projects using Bugzilla we have enabled the optional 'Target Milestone' field to indicate when a bug is planned to be fixed. It is extremely helpful for bug triage. Unfortunately that field is enabled globally and not on a per project basis so it is not viable for this effort.
-Mark -----Original Message----- From: Glen Daniels [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 25, 2002 4:23 PM To: '[EMAIL PROTECTED]' Subject: RE: Bug state I was going on the assumption that we'd try to clear the bug list for the beta, and mark everything we weren't going to deal with as LATER. But perhaps you're right and we should leave them as ASSIGNED. Be nice if we could add our own new status fields like "FIX4BETA2".... --G > -----Original Message----- > From: Tom Jordahl [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 25, 2002 4:20 PM > To: '[EMAIL PROTECTED]' > Subject: Bug state > > > > If the state is changed to "RESOLVED", then the bug doesn't > appear on the list of bugs left to fix. I realize I can > change the query to catch these, but wouldn't it just be > better to leave them in the open and assigned state? > > -- > Tom Jordahl > > > > [EMAIL PROTECTED] changed: > > What |Removed |Added > -------------------------------------------------------------- > -------------- > Status|NEW |RESOLVED > Resolution| |LATER >
