🔒 Locked
Bug tracking software
Advertisement
Original Post
I've been happy with Trac - it does a bit more than just bug tracking (with a wiki and optional SVN integration) but it's still fairly easy to set up (assuming you're able to run Python) and to use, and it provides all the bug-reporting and categorising and listing that I've wanted. It seems to be used quite widely by medium-sized projects (Google suggests WordPress, Django, RoR, etc), and it also has a nice way of supporting extensions to add less common features.
Trac, perhaps? (Example installation)
Quote:
Original post by superpig
Mantis is what I generally choose to use for projects these days. Not hard to set up if you've done it before, small but focused featureset, and pretty easy to extend and interface with. The only problem I have with it is that it's written in PHP.
You'd prefer an ASP bug tracker, I suppose?
http://www.bugzilla.org/
But the thing is I don't think it's that simple. I've been looking in to this recently myself.
Trac is great but single project per install. You can have lots of single projects but they can't talk to each other easily. I'm not confident of it scaling particularly well right now. Bugzilla is proven but huge and doesn't have easy subverion integration from what I can tell.
I'll extend the original posters question - does anyone know of a freebie bug tracking system that integrates the Bugtraq properties of subversion, issue tracking across multiple projects, and leaves space for wiki integration?
It would be great if a developer checked in and commented a changeset, used the issue id, then the bug tracking system automatically updated that. And it all worked with Continous Integration (Cruise Control .Net say). And let you see the diffs.
I have managed that above paragraph with a Subversion, Cruise Control.Net, Trac installation, but for a single project. As each Trac install is more or less independant, there could be issue id collisions etc, and possible duplication in the wiki components.
I've found something called scmbug which promises bugzilla + subversion integration, but I can't get that to compile / work.
Has anyone got any experience getting Mantis or anything else free doing things like I want above?
But the thing is I don't think it's that simple. I've been looking in to this recently myself.
Trac is great but single project per install. You can have lots of single projects but they can't talk to each other easily. I'm not confident of it scaling particularly well right now. Bugzilla is proven but huge and doesn't have easy subverion integration from what I can tell.
I'll extend the original posters question - does anyone know of a freebie bug tracking system that integrates the Bugtraq properties of subversion, issue tracking across multiple projects, and leaves space for wiki integration?
It would be great if a developer checked in and commented a changeset, used the issue id, then the bug tracking system automatically updated that. And it all worked with Continous Integration (Cruise Control .Net say). And let you see the diffs.
I have managed that above paragraph with a Subversion, Cruise Control.Net, Trac installation, but for a single project. As each Trac install is more or less independant, there could be issue id collisions etc, and possible duplication in the wiki components.
I've found something called scmbug which promises bugzilla + subversion integration, but I can't get that to compile / work.
Has anyone got any experience getting Mantis or anything else free doing things like I want above?
The FAQ says you can have multiple projects on one box with the Trac code installed once, but each project would go in a separate "environment" with its own database and would work independently of the others.
Depending on what you consider 'multiple projects' to mean, if they're all in a single SVN repository then you could have a single Trac environment and just use the "component" field of a bug to say what project it corresponds to; and then make reports that list only the bugs belonging to a single project. But it's not going to work quite as well as Bugzilla when you want to have dozens of products split into several hundred components and with a third of a million bugs, so don't use it for that [smile]
Depending on what you consider 'multiple projects' to mean, if they're all in a single SVN repository then you could have a single Trac environment and just use the "component" field of a bug to say what project it corresponds to; and then make reports that list only the bugs belonging to a single project. But it's not going to work quite as well as Bugzilla when you want to have dozens of products split into several hundred components and with a third of a million bugs, so don't use it for that [smile]
Quote:
The only problem I have with it is that it's written in PHP.
That's actually a plus, right? :-)
If you have lots of projects, I'd go for bugzilla. It's been tested for a long time, and has excellent reporting features. Mantis is a good second, and probably easier to install.
I can throw in my suggestions here as well. I have been trying to find a good issue tracker for a long time. So what I found was TodoList it's a good program to keep track of all kinds of things.
Lately I found a fully featured issue managment program that's free for a single developer. It has a web interface, Visual studio integration and a windows client. It's called OnTime. I'm a single developer so it's perfect for me. Quite cheap for 5 or 10 persons if the need should araise. The reason I like this program is that it has a tree based project list. It has possibility to report bugs through the web and it has a windows client.
The bad thing with it is that it's a bit slow when refreshing the lists. I hope they fix that in the next release.
Lately I found a fully featured issue managment program that's free for a single developer. It has a web interface, Visual studio integration and a windows client. It's called OnTime. I'm a single developer so it's perfect for me. Quite cheap for 5 or 10 persons if the need should araise. The reason I like this program is that it has a tree based project list. It has possibility to report bugs through the web and it has a windows client.
The bad thing with it is that it's a bit slow when refreshing the lists. I hope they fix that in the next release.
I use Mantis. I was able to expand it to have an electronic form of an NDA that did not allow testers to access project information until they accepted the NDA.
There are a few other things that I can not think of off the top of my head that I wish it had, but I think I will just mod them in as well.
There are a few other things that I can not think of off the top of my head that I wish it had, but I think I will just mod them in as well.
Quote:
Original post by Trip99
Are any of these particularly good or bad at supporting many small projects?
Depends on your server platform, as much as anything else. Open source people can be very lax / anti about putting things on closed Windows.
Bugzilla is the daddy but ugly (though you can skin it), Mantis I've not used but some very respectable people have piped up on this thread to say they do, Trac is great but as it's not even at version 1 yet requires a little fiddling and apache know how to do the multiple project thing. Flyspray I like the look of where they are going with it, Dokuwiki is an awesome wiki.
I think it is fair to say that Bugzilla probably has the biggest community out of all of them, very active forums and such. Mantis also looks very active. Trac is full of hackers and developers that just love it and coding for it. Flyspray seems a little more smaller but if you like the look of it, maybe.
Bugzilla certainly can scale, as I hear Mantis can. Trac has yet to be proven with tons of little projects working together, though someone I'm sure could prove me wrong.
I really like Trac, it's feature set is awesome. Yet I'm struggling to use see how to apply it at work to our many projects. If it were a little more mature then I reckon it could beat most of the others hands down.
Topic Locked
This topic has been locked by a moderator. New replies are not allowed.
Sign in to reply to this topic.
Advertisement