Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

bugzilla and the crawling chaos 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I too spent more than a few hours hacking bugzilla into something more usuable, and have recently revisited it with the Mayfly project - essentially porting it to Class::DBI and Maypole.

    I haven't had a chance to build the maypole side yet but I have some CDBI classes that work with an existing bugzilla database.

    I am giving very serious thought to breaking backwards compatbility and providing a migration script rather than keeping the bugzilla database exactly as it is.

    let me know what other bits you'd like
    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • Well, if mayfly doesn't fix the serious usability issues with bugzilla's interface, not mentioning the unability to write plugins and so on, I don't think it's worth considering. Have higher goals! Even if your project approaches 10% of RT it will still be much better than the bugzilla abomination.
      • I have been thinking about setting up a bug tracker and a support ticket/tracker and have been mentally debating whether or not these two needs should be served by a single application. I usually think of RT as being more in the support ticket category but obviously it can be used for both (rt.cpan.org). How well, though, does it compare against other tools designed specifically for bug tracking?
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.