Keith Fetterman <[email protected]> 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.
pgplPlrexUvXJ.pgp
Description: PGP signature
