Trac Spam

[Peter Hosey]

On Nov 28, 2010, at 14:13:35, Christopher Forsythe wrote:
> What I'm talking about could be done on google code, bitbucket, jira,
> or even a very well done text document system with folders and files.
> And yes trac can be used to accomplish the same thing.

That said, I *would* advocate a fresh start with an empty ticket database (keeping the old Trac around in read-only mode for migration of debug logs, etc.), whether it's on Trac or something else.

Being able to find duplicate tickets is pretty easy when nearly all of the tickets were filed by developers or sophisticated users. It's much harder, for *anyone*, when searching 10,000 tickets of widely varying quality, and when half of those tickets are themselves duplicates.

I suggest starting with an empty ticket database, re-filing everything in the 1.4.2 and 1.5 milestones, and filing anything else as it comes in as if the former ticket DB never existed.