Roger Oberholtzer wrote: > On Tue, 2011-02-08 at 08:52 -0500, Chris Nelson wrote: >> Roger Oberholtzer wrote: >>> I have added the sub-ticket macro from Trac Hacks and am looking >>> forward to using it. I would like to investigate reorganizing some >>> tickets to have this relationship. It appears to me that a >>> sub-ticket added to a ticket must be a new ticket added via the >>> 'add' button. Is that the only way? Is there no way to make an >>> existing ticket into a sub-ticket? The parent ticket is a newly >>> added ticket, so it has all the required variables. If that makes >>> any difference. >> >> As I reorganize tickets using Subtickets, I go to the child and type >> the parent ticket ID into the Parent Ticket field. > > Well shucks. That is just too easy. Grin. > > Even better, it seems to have worked!
Great. > Then I did something really stupid... > > I set the parent ID on some tickets using the batch modify macro. That > seems to have worked. I very stupidly set the parent ID on the parent > ticket to itself. So I cannot see this ticket. trac eventually fails > with: > > RuntimeError: maximum recursion depth exceeded in cmp > > Any idea how I could remove this value from the problem ticket? I am > guessing I need to use some SQL. And here is where my knowledge ends. The subtickets relation (table) is much like the mastertickets relation. Remove any row where the parent and child are the same ID. -- 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.
