Thanks all for the help and being patient. There is this problem with most of the documentation on Trac plugins. If you don't know the lingo you are lost.
I think I understand now what "blocked" means in this context. For some reason, the "blocks" and "blocked by" fields in my tickets are greyed out. It must mean that I do not have my trac.ini configured properly. I have the default: [ticket-custom] blocking = text blocking.label = Blocking blockedby = text blockedby.label = Blocked By What does the "... = text" do? Does that define what kind of field goes there? Can I configure select, etc? The plugin is enabled. Any ideas for other reasons my fields would be grey? Thanks, Ariel Greg Troxel wrote: > 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. > -- /\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\ Ariel I Balter, Ph.D. Postdoc Biological Monitoring/Modeling Fundamental and Computational Sciences Directorate Pacific Northwest National Laboratory Mail: PO Box 999, MS P7-58,Richland, WA 99352 Shipping: 790 6th Street, MS P7-58, Richland, WA 99354 Tel: 509-376-7605 Cell: 509-713-0087 [email protected] www.arielbalter.com www.pnl.gov --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
begin:vcard fn:Ariel Balter, PhD n:Balter;Ariel email;internet:[email protected] tel;home:812-332-2721 tel;cell:812-219-4558 x-mozilla-html:TRUE url:http://arielbalter.com version:2.1 end:vcard
