it's not very good.. i'm working on version 2, but it uses SQL. the demo is down, but it's very basic. [bugs.ikonboard.com...] is the only site i can find that is using it. they modified the template a smidge, of course.
Don't get me wrong, I personally love perl. I use perl for most of my system programming. But I don't use it for webpages.
When I create webpages I find PHP much easier to script in. PHP was designed directly for creating webpages. PHP stands for something like "Personal Home Page" language. Perl is the duck tape of programming languages. It will do almost anything almost anywhere. You can still find lots of programs written in Perl. But it looks like the web world is slowly migrating over to PHP for web apps.
Perl requires lots of extra work like importing and other things like that. In PHP I can spit things out right in the middle of my HTML like this <?= date("Y"?>, and that would have shown the current year. Now that is pretty darn convent in my book.
My comment was because I know Brett is a die hard Perl guy and I recall the last bug tracker I set up for someone was called, Mantis, and that was PHP based. But if we take a look at Freshmeat we will see there are plenty of Perl Bug Trackers out there.
Here is a list of Perl Bug trackers [freshmeat.net](30)
Here is a list of PHP Bug trackers [freshmeat.net](25)
Most of them will require DB back end I think. There were two products that we have evaluated at work before - Bugzilla [bugzilla.org] and Request Tracker [fsck.com]. However, both of them are quite difficult to set up, and are quite complicated - thous might not be suitable for small jobs. RT requires mod_perl and Mason I think, and I could not remember what Bugzilla requires. At the end, we went with a PHP solution (Mantis [mantisbt.sourceforge.net]) because it is much easier to integrate it with our current service.
And with PHP and Perl - well, Python rules them all :)