Oh wow, I inherited this system and didn't even realize we were using a plugin for that functionality.
Thanks for the quick response! -ryan Noah Kantrowitz wrote: > That disclaimer on the MasterTickets wiki page that says "The 0.10 > version of this plugin suffers from many systemic design flaws." isn't > for giggles. Do not use it. If you want to use MasterTickets, upgrade > to 0.11dev. > > --Noah > > On Feb 11, 2008, at 4:05 PM, J. Ryan Earl wrote: > > >> Hello list, >> >> I searched the list archives, but didn't see anything about this >> particular problem we're having. In fact, I think we found an error >> in >> Trac. >> >> We have a weird situation where blockers are being associated with >> incorrect tickets, but the numbers of the tickets are related at a >> lexical level. For example: >> https://svn.enthought.com/enthought/ticket/1234 blocks >> https://svn.enthought.com/enthought/ticket/1235, however, >> https://svn.enthought.com/enthought/ticket/235 is also showing up as >> being blocked by ticket:1234. This problem is also manifesting itself >> on some newer (<2 week old) internal project Tracs. >> >> Has anyone seen behavior like this before? Any idea what may be a >> solution for it? Any help would be appreciated. >> >> Thanks in advance, >> >> J. Ryan Earl >> IT Administrator >> Enthought, Inc. >> 512.536.1057 >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
