Quick noob question: How does one use the MasterTicketPlugin? I will assume you have of course read http://trac-hacks.org/wiki/MasterTicketsPlugin
In general, how does one build a ticket hierarchy? The MasterTickets enables expressing directed edges between tickets, so you can store "ticket #A blocks ticket #B". It does not define what those edges mean exactly. You can add edges by editing the blocking/blocked-by fields on an existing ticket and saving it, or putting a value in the fields when you create a ticket. Q1. What does 'blocked' mean in the trac.ini file? huh? my trac.ini doesn't have that. the MasterTickets plugin adds two new ticket fields, blocking and blocked-by, and those are populated using the mastertickets sql table. trac.ini defines their name and display values. Q2. How do I create a ticket that will allow sub-tickets? MasterTickets does not have the concept of "sub-tickets". Any ticket can be blocked by any other ticket; you don't have to do anything special. Q3. How do I add sub-tickets to an existing ticket? You can't because there are no sub-tickets. But you can make a new ticket and put "blocking: #X" as you add it, and then the new ticket will appear in X as blocked-by and have blocking: X. Q4. How do I make a sub-ticket to a master ticket? Again this question doesn't make sense. I can think of two sensible ways to use MasterTickets. One is to express that ticket #B cannot be accomplished until ticket #A is resolved, and I'd call this the normal mode of use. The other is to say that task #A is composed of tasks #B #C #D. Here you'd put blocking: #A in each of #B #C #D. You would expect that B C and D can be done in any order, and that once all three are done A is done more or less by definition. My post was about wanting to use both ways at the same time.
pgpkht1mTIUZf.pgp
Description: PGP signature
