On Wednesday, September 16, 2015 at 9:44:04 PM UTC-7, RjOllos wrote: > > > > On Wednesday, September 16, 2015 at 5:10:54 AM UTC-7, Greg Troxel wrote: >> >> >> With >> >> trac-1.0.5 Repository browser, wiki, and issue tracking system >> trac-plugins-MasterTickets-3.0.4.12946 Ticket dependency plugin for Trac >> >> I tried to close a ticket A that had a blocking open ticket B. I got a >> page with a warning about B, and showing A as closed. But asking for >> the A page again shows it open. >> >> So I think something's wrong in how the mastertickets can-close hook >> stops the closing but not the rendering of the ticket as closed. >> > > The plugin is in pretty bad shape and I haven't had time to fix it. When I > find time I'm also more inclined to spend time backporting Bloodhound > TicketRelationsPlugin to Trac, which is a more generalized replacement for > MasterTicketsPlugin (and SubticketsPlugin). > > The major task for MasterTicketsPlugin is to modify the database > transactions to be atomic, so that the database cannot get into an > inconsistent state. The situation you describe sounds similar to some of > the open tickets I've read through in the past. You might have some success > upgrading to 4.0dev and manually fixing your database. > > For future reference, user issues should be directed to the trac-users > mailing list: > http://trac.edgewall.org/wiki/MailingList > > - Ryan >
There's a 4.0.0dev for MasterTicketsPlugin that is compatible with Trac 1.0+. I'll create the release as soon as there is sufficient feedback. - Ryan -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
