Chris Nelson <[email protected]> writes: > Greg Troxel wrote: >> I am currently using 0.11.4 with MasterTickets and >> TimingAndEstimation. > > Me, too. > > >> We use blocking/blocked-by for two separate meanings: >> >> Can't do X until Y is done. >> >> Ticket A comprises subtasks AA AB AC AD AE. >> >> The second case is exactly what you need to represent a Work Breakdown >> Structure in trac. > > Yes! > >> I propose to use blocking/blocked-by >> for the first, and parent/child for the second, with edges pointing >> from a ticket to each child. > > I imagine tickets would have a 'children' field and a 'parent' field.
Yes, but these would come from edges stored in the mastertickets table in the db. The children field would be all tickets for which there is a me, X, child row in the table, and parent would be Y, me, child with an integrity constraint that there is only one Y. > My PM page at Trac-Hacks (http://trac-hacks.org/wiki/ > ProjectManagementIdeas#Dependencies) speaks to this. > http://trac-hacks.org/wiki/ProjectManagementIdeas#TracPlugins makes > references to the SubTickets proposal which directly addresses your > need. http://trac.edgewall.org/wiki/SubTickets This seems like a much bigger change than I am proposing. I am just trying to express the hierarchy so I can write reports to query things. It would be useful to show only top-level tickets in queries, and to allow expanding them. In my project I expect to have high-level tickets on a milestone and subtickets on earlier milestones, so I don't want to simply suppress subtickets. But, if the expression of edges was done, then the rest of the subtickets proposal could be tried out. > As my immediate focus is scheduling but I want to plan for parent/ > child, I've thought a lot about how to roll-up data from child > tickets. Considier: > > * Task A consists of subtasks AA and AB, > > * AA takes 16 hours and Arthur is working on it 50% of his time so > it'll take 4 days, and > > * AB takes 24 hours and Brian is working on it 40% of his time so > it'll take 7.5 days, > > What do the resource allocation and duration of A look like? A has 40 > hours work. If AA and AB have no dependencies, the overall duration of > A is the longest duration of a subtask (7.5 days). That's controlled > by Brian's effort so if Arthur has to do 16 hours in 7.5 days, or 26% > (I think). I would say that A does not get allocated resources, just AA and AB, and A's planned start time is the earlier of AA and AB, and planned end the later, and that's that. In your example AA will be done in 4 days and AB 7.5 so that's A's finish time. Scheduling is probably on my list too - just not my immediate problem. I don't think there is a conflict between WBS and scheduling.
pgpcDqIhC1Cbx.pgp
Description: PGP signature
