On Wed, Mar 04, 2009 at 05:47:50PM -0800, Max Kanat-Alexander wrote: > On Wed, 4 Mar 2009 15:38:45 -0800 Danek Duvall <danek.duv...@sun.com> > wrote: > > Hm. Free text fields are definitely not okay, > > You can add custom select fields, too.
Yup. Thing is, its data needs to draw from the same pool as the product's version, which means custom code as well. It hasn't been enough of a bother for our project to make me go do that. In experimenting with custom fields, though, I noticed it's not possible to remove one. You can mark it obsolete, but once it's there, it's there. Even if no bug has any data for it. > > and I'm not aware of a way to require a "resolved in version" field to > > be filled in when changing state, only that a comment is required. > > It's not that difficult of a customization. Probably not, but it's something that would need to be done to bring our bugzilla instance up to parity with bugster. Danek _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
