I don't know if it makes any practical difference, but I wonder if we should decide to use either "Resolved" or "Closed", but not both. Right now, we seem to be using either/or, willy-nilly.
Following up on Don's observations, my preferences would be to keep it simple and just use Resolved and forget about Closed. (Or vice-versa, since we can edit Closed tickets too.) -Ted. On Aug 9, 2007 12:32 AM, Don Brown <[EMAIL PROTECTED]> wrote: > I believe the traditional purpose of the "closed" state is for a QA > department, so they can mark the issues they have verified to be > fixed. In Struts, I don't think we really do that, and while we do > informal code reviews (commit emails), we certainly don't require > formal test documents that verify the ticket resolution is correct. > If a release manager wants to take that role upon themselves, that's > great, but it should be purely optional. > > Don --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
