Yes it would be nice if there were a target field to indicate when the defect would be addressed. So then we could indicate that a bug was open but targeted for a later release.
Rich Scheuerle
XML & Web Services Development
512-838-5115 (IBM TL 678-5115)
Glen Daniels
<gdaniels@macrome To: "'[EMAIL PROTECTED]'"
<[EMAIL PROTECTED]>
dia.com> cc:
Subject: RE: Bug state
04/25/2002 03:23
PM
Please respond to
axis-dev
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
>
