On 18.08.2012 16:23, Sam Halliday wrote: > I have seen that both MasterTicket and SubTicket plugins are trying > to accomplish the same thing.
As I see it both of those plugins supply different things. And it is normal to have both installed. Subticket is representing ticket hierarchy, for example you have a big task that is divided into smaller tasks (=child tickets). All of those tickets are somehow related. Mastertickets and fields blocking/blockedby are exactly for that - indicating that some ticket is locked by some other, and those tickets can be totally unrelated. For example: ticket #123: Extending internal trac to support ordering coffe is blocked by ticket #234: Deliver second monitor to developers Rationale: i can't develop without two monitors on desk But those tickets don't share a hierarchy, are not part of the same bigger task, etc, etc. > But what functions do these plugins really provide? What are they doing > that I can't already achieve with the following in my [custom-tickets] ? > > blockedby = text > blockedby.label = Dependencies > blockedby.order = 5 > blocking = text > blocking.label = Parents > blocking.order = 6 Mastertickets automatically fills the corresponding field in the second ticket - if you set blockedby #2 on #1, then blocking is set to #1 on #2. Generally both of those plugins supplie some automation in filling those custom fields. Without them it would be tedious to keep everything in sync. Hope this helps. -- silk -- 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.
