On Jun 27, 2:22 am, "Daniel Lowicki" <[EMAIL PROTECTED]> wrote: > Hi all, > > a bug may require several developers to patch something - possibly in > different modules. > > What is a good strategy to keep track of the progress? Something like > sub-milestones? > > At the moment I can only think of assigning the bug to an owner - > keeping him in charge of the "project" and letting him close the ticket > when all others report "done" to him. > > How do you facilitate this? > > br > > Daniel
This seems like a perfect use for the MasterTickets plugin. It still leads to what you're saying with one person on top of the "project" to fix it. we also added a custom field called "Module" or similar. the component is high level (hardware, Software, OS) and has the appropriate default owner who is a lead engineer, we then internally map modules to the junior engineers (usually the leads do that actually), so they have initial visibility of all the "master" bugs due to the component, then they assign the blocking tickets based on the module. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. 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 -~----------~----~----~----~------~----~------~--~---
