On Nov 15, 6:48 am, Greg Troxel <[EMAIL PROTECTED]> wrote: > I think of milestones as deliverable functionality and I use tickets > as items in my To Do list (typically a day's work or less) so I can > see progress as tickets are worked on and closed. But that leaves me > with a big gulf of resolution between a ticket and a milestone (which > might be weeks or months of work). > > I really want to organize tickets into a hierarchy so "Implement the > new Frobnitz" can have child tasks of "Implement Frobnitz data > structures", "Implement Frobnitz user interface", "Add error checking > to Frobnitz runtime", etc. I don't see a good way to do that in trac. > Is there a plugin I've missed? > http://www.trac-hacks.org/wiki/MasterTicketsPlugindoesn't really fit > the bill. > > I have the same issue - mastertickets lets you associate the tickets, > but doesn't roll up progress to sub milestones. I think you might want > the MasterMilestonesPlugin but I don't think anyone has written it yet. > It would let a milestone have a parent milestone, and have the milestone > display find all tickets also from all child milestones - that might not > be that hard to do. > > application_pgp-signature_part > < 1KViewDownload
Well, for me MasterTickets does the trick. But I don't work on a daily basis. We create a master ticket for a feature branch.... sounds like what you want is: http://trac-hacks.org/wiki/ProgressMeterMacro if you happen to use, say a checkbox for "active" for example: [[ProgressMeter(status=closed|ready for QA, owner=$USER,active=1 , milestone=CurrentMilestone)]] or something. you could just macro something like: --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
