Earlier quoted context omitted.
I'm going to second Trac. I'm using it primarily because of its easy integration with Subversion.
Indeed. I just started using it, and it's quite good. Has anyone experienced a speedup by not using the built in server?
Ask YC: Your bug tracker
11–20 of 32 posts
Re: Ask YC: Your bug tracker
#12I've used Bugzilla, Mantis, JIRA, Netbeans' bug tracker, and FogBugz and found that they all basically suck. So I'm just going to give you a list of features that I'd like to see: 1.) A clean & simple UI. Reporters should just have a text field to enter the bug description and a way to attach screenshots/tracebacks/logfiles/tests/patches. All the priority/component/version/milestone/assignee stuff should be filled in…
It covers most of your points but doesn't include bug reporting/tracking by people not on a project (e.g., users). Their API and email integration should make it easy to integrate your own "report a bug" form.
Re: Ask YC: Your bug tracker
#13We use Trac at Justin.tv. The only thing that really bothers me is that it's kind of slow - up to 2 seconds to load a page. Other than that, it seems "good enough", but I'm sure there are advances to be made that I've never thought of.
svn commit -m "Stopped electrocuting users, fixes #4959."
Re: Ask YC: Your bug tracker
#14I submitted a similar idea as a last second YC application. Basic points of differentiation were that it would be fully extensible (add/remove any input fields), and that it would have a killer API. The API would allow you to submit issues from anywhere you please: you could write a plugin for Eclipse (or favorite IDE) or you could widgetize it into a js include file so people could submit issues directly from your w…
Re: Ask YC: Your bug tracker
#15Earlier quoted context omitted.
I'm going to second Trac. I'm using it primarily because of its easy integration with Subversion.
Indeed. I just started using it, and it's quite good. Has anyone experienced a speedup by not using the built in server?
Re: Ask YC: Your bug tracker
#16We use Trac at Justin.tv. The only thing that really bothers me is that it's kind of slow - up to 2 seconds to load a page. Other than that, it seems "good enough", but I'm sure there are advances to be made that I've never thought of.
Re: Ask YC: Your bug tracker
#17Re: Ask YC: Your bug tracker
#18We use Trac at Justin.tv. The only thing that really bothers me is that it's kind of slow - up to 2 seconds to load a page. Other than that, it seems "good enough", but I'm sure there are advances to be made that I've never thought of.
I love the way Trac integrates with subversion. A friend of mine even wrote a nice plugin that allows you to close a bug in Trac just by doing an svn commit, by writing stuff like: svn commit -m "Stopped electrocuting users, fixes #4959."
Re: Ask YC: Your bug tracker
#19I've used Bugzilla, Mantis, JIRA, Netbeans' bug tracker, and FogBugz and found that they all basically suck. So I'm just going to give you a list of features that I'd like to see: 1.) A clean & simple UI. Reporters should just have a text field to enter the bug description and a way to attach screenshots/tracebacks/logfiles/tests/patches. All the priority/component/version/milestone/assignee stuff should be filled in…
They also offer svn hosting, but that is optional. (you can simply use them as a bug tracking system)
They've been very responsive to feature requests and have fixed several bugs/issues that we complained about, when they were still in their early days.
Re: Ask YC: Your bug tracker
#20We use Trac at Justin.tv. The only thing that really bothers me is that it's kind of slow - up to 2 seconds to load a page. Other than that, it seems "good enough", but I'm sure there are advances to be made that I've never thought of.
I'm going to second Trac. I'm using it primarily because of its easy integration with Subversion.
Anyone offer an outsourced, hosted version of Trac? =)