Hi, There have recently been a discussion that could be relevant to this one here: http://groups.google.com/group/trac-dev/browse_thread/thread/d07c7ed673eb170e#
Although that won't help you detect duplicates when they're already entered in the system. However, the mechanism for searching for duplicates would probably be quite similar if you search for duplicates before or after entering them.. I encourage you to start working on such a feature =) On Sun, Apr 6, 2008 at 11:26 PM, Alec Thomas <[EMAIL PROTECTED]> wrote: > > On Sun, Apr 6, 2008 at 11:13 PM, Yguaratã C. Cavalcanti > <[EMAIL PROTECTED]> wrote: > > I've made some investigation on Trac tickets and realized that almost 23% > of > > the tickets are duplicates. Is this type of tickets really a problem to > > people that have to analyze them (in Trac)? Some academic work have > > addressed this problem telling that it is very serious, thus i want to > > confirm with you too. > > Hi, > > It's certainly very time-consuming dealing with duplicate tickets. If > you provided a patch that implemented robust duplicate detection, I > suspect you would make many new friends :) > > Alec > -- > Evolution: Taking care of those too stupid to take care of themselves. > > > > > > -- Med vennlig hilsen Erling Wegger Linde --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
