Projects / bugtrack

bugtrack

bugtrack is a Web-based bug tracking system written in Perl. It supports multiple users and projects with multiple components and versions, provides e-mail notification, and should work with any DBI compliant database.

Tags
Licenses

Recent releases

  •  21 Jan 2002 16:37

    Release Notes: The new features in this release include privilege sensitive links, session management, and the ability to switch projects without logging out. The cookie format has changed, so please delete your browser's cookie prior to using version 2.9. You must also run the database patch if you are upgrading.

    •  16 Oct 2001 06:02

      Release Notes: SMTP support, delete confirmations, and CVS caching added.

      •  19 Jul 2001 16:41

        Release Notes: The concept of user roles was removed in favor of privileges. Now you can set privileges to add, edit, and delete projects, users, filters, and reports on a per-user basis. You can also set privileges to add, edit, and delete bugs by user on a project by project basis.

        •  28 Jun 2001 05:53

          Release Notes: This release includes localization support (with modules for English, Italian, and Spanish), the ability to associate a CVS repository with a project, and the ability to associate bugs with files from the repository.

          •  21 Jun 2001 03:39

            Release Notes: A new title search capability, removal of subqueries (MySQL can't do them), a fix for a memo field/DBI problem with MS Access, and a fix for a problem with MS Access when filter ID is null.

            Recent comments

            22 Sep 2000 09:35 agstools

            Why did I write bugtrack?
            I am currently using bugzilla and was also responsible for setting it up on our system. We primarily use postgres and had never used mySQL before. Setting it all up was a bit of a challenge. The database design is not portable either.

            This was partly "just for fun" and to make a more portable program with a simplier interface. I have tested this with postgres/apache on linux and access/omnihttpd on windows. The only non portable data type I believe I used was "serial" for postgres and "counter" for access. Also more of the parameters are user definable.

            Setup should be easier too. There are only 6 required files (over 60 for bugzilla) and no dependencies on other stuff like bonsai, etc.

            Again, it was fun developing and I'd definitely appreciate ideas!

            22 Sep 2000 08:14 walles

            How is this different?
            How is this different from Jitterbug and Bugzilla? Why should I use this instead?


            Cheers //Johan

            Screenshot

            Project Spotlight

            OpenStack4j

            A Fluent OpenStack client API for Java.

            Screenshot

            Project Spotlight

            TurnKey TWiki Appliance

            A TWiki appliance that is easy to use and lightweight.