Bug Tracking

[clange]

Hi

I have decided to start using some form of bug tracker for my OS project. I have so far just used a simple text file which has served my purpose quite well. But I have decided to put my bug list online. It would be too time consuming and error prone to do by hand but a web based bug tracker would give me this for free. I am therefore looking for a simple bug tracking tool. I have tested flyspray but it seemed a little bit complex considered that I am the only developer.

So I would like to know if any of you know of a simple bug tracker?

My requirements:
- Simple
- Open Source
- PHP or ASP (this is all my host provides)

Also how do you manage bugs etc. in your OS project?

Thanks in advance

clange

[JohnnyTheDon]

http://www.mantisbt.org/

[clange]

Hi

Mantis seems to be a bit overkill for my purpose. Do you have any experience with it?

clange

[JohnnyTheDon]

I use it at where I work to manage bugs for some internal company programs. It seems to run well. I'm not saying its necessairily the best solution out there, but it works.

[Solar]

With the PHP restriction, my vote would go for Mantis, too. I've set up a Mantis some time ago, and it was pretty neat to use.

Without the PHP restriction, my vote would be on Trac (Python), which nicely integrates a bug tracker, wiki, and Subversion frontend.

[clange]

Trac would be my first choice too without my PHP restriction.

I decided to install and play around with both Flyspray and Mantis and I also just discovered http://eventum.mysql.org/wiki/index.php/Main_Page. I'll let you know what I choose and why.

Thanks for the feedback to both of you.

clange

[clange]

Notes about choosing a bug tracker

My requirements are:
- I mainly need a simple bug tracker
- I will be the only user adding issues
- The purpose is to be able to have a public list of bugs
- It has to be PHP since this is what my host provides

I looked at Flyspray, MantisBT and Eventum. I quickly rules out Eventum since I didn't really like the look of it and it seemed to put a lot of focus on work flow (which I don't need) and I didn't like that I had to sign up before downloading it.

Both Flyspray and Mantis fulfilled my requirements perfectly. For my usage with only one super user adding content and all other users only being able to browse the list of issues Flyspray worked “out-of-the-box”. Mantis required a little bit of setup but how to do it was easily found with a few Google searches.

Since I don't like the default look of any of the 2 systems I tried to find an easy way to skin them. But without success.

In the end I decided to choose Mantis. I think it will be more useful in my professional life and I liked the default look a little better. There also seems to be more support for Mantis than Flyspray.

clange

[clange]

Too lazy to write my own that's why I decided to use an existing bug tracker. But the concept of distributed bug tracking seems nice (although over kill for my purpose).

clange