Greg, Thank you for responding. I really appreciate it.
I can see your point that total ordering isn't necessary, and I can see it will take a lot of effort updating the ordering as priorities change. I am still at a loss to understand how best to manage the tickets that are not "accepted". I can see your idea on keeping the "accepted" tickets to the ones you are currently working on or will work on this week. If you can figure out what you need to do next, that's most of the > battle. Figuring out what can fit in a month/quarter is useful too, > but strictly ordering them doesn't seem necessary. This is what I am really trying to understand in how to effectively use Trac to manage. If I have 150 open tickets in Trac, grouped into 6 categories, what is the best way to identify the tickets that should be worked on following the ones currently being worked on? We are not using Trac to manage the development of a software product. If we were, I guess we would be grouping these tickets into milestones, and periodically, the development team would be meeting to discuss which tickets would be in each milestone. Then each developer would choose their "accepted" tickets from the current milestone pool of tickets. Then I am also assuming that tickets that are assigned to a version, would also need to be grouped into a milestone. We are using a single instance of Trac to manage changes to a Web site and other applications, and we are using Trac to manage system administration tasks. Where I get confused in using Trac is when we have a large number of tickets that are a "Major" or "Minor" priority and some of these tickets should be worked on before others, how do you put them into some kind of order. I appreciate your feedback and helping me how to effectively use Trac. Keith On Friday, December 7, 2012 8:46:41 AM UTC-8, Greg Troxel wrote: > > > Keith Fetterman <[email protected] <javascript:>> writes: > > > What is the most effective way to use "accepted" versus "owned", and > rank > > the lists in the order you plan to work on them? One thought I had was > to > > mark the tickets I am currently working on as "accepted". The other > > tickets that I will be working on in the future will be marked as > "owned". > > My take is that 'accepted' should denote that you are actively working > on the ticket. However, accepted vs assigned to you is really a matter > of communicating within your project team, and there is no extrinsic > right and wrong. > > > The problem with this is the size of the "owned" tickets becomes quite > > large and they are also not rank ordered in the order I need to work on > > them. They are grouped by priority, but the groups are large and I > don't > > have a way to rank each group. > > I don't understand why you feel the need to create a total ordering of > all of your tickets. My advice is that once you've figured out what > you'll do this week, accept those, do it, and repeat. > > Overall I have three bits of advice: > > You should have this discussion with your project team. The team > should have written norms that explain the work process, or at least a > shared understanding. > > If you can figure out what you need to do next, that's most of the > battle. Figuring out what can fit in a month/quarter is useful too, > but strictly ordering them doesn't seem necessary. > > If you really must order, you (or the trac admin, rather) can add a > new field to trac, and you can put in integers from 0 to 100, and you > can sort by that. But I don't think that's a good use of effort. > > > > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/trac-users/-/dfQVBWaabqwJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
