From: Mark M. <mie...@gm...> - 2012-08-19 19:59:36
|
On Sun, Aug 19, 2012 at 12:43 PM, Rick McGuire <obj...@gm...> wrote: > One problem I had with the old tracker system was managing items that needed > multiple updates to complete. A good example are the enhancements, which > typically require updates to code, docs, and test cases. Looking at the > system, I think we can use the labels capability to mark what sort of > additional activity are needed for an item. All we need is a convention. I agree with this, I've been thinking along the same lines, that we just need some conventions that we are all aware of. > For example, adding labels of NEED_DOC or NEED_TEST would indicate this item > still needs these additional pieces. These tags can be removed once those > pieces are complete, so we have a better method of seeing what work still > needs to be done to an item. Thoughts? I think that as we use the new system a little bit we can probably figure out how to use it better. I think we can set the tools up better. For instance, it might be better to add a new field rather than add agreed upon labels. I think, but haven't tried it yet, when you add a new field, you can specify the type of field. One type of field, again this is speculation at this point, one type of field is like a combo box and you can specify what values are available in it. Well, I take it back about being better for your example. In that example, agreed upon labels are better because you want several labels for one item. I think my point was that there are probably other areas in the tools that we can make good use of if we have a consensus on what to do in those areas. -- Mark Miesfeld |