Live data from Hacker News

Poll: What do you use to track your bugs?

news.ycombinator.com

51–60 of 76 posts

Re: Poll: What do you use to track your bugs?

#52
vi BUGS.txt

for as long as reasonable

thought that file's length should be 0 (for as long as reasonable, and even then, should only be due to bizarre/unreproduceable platform causes, not a direct flaw in your application source)

yes this system works best if 1 programmer. but 1 programmer is the ideal team size, if you can achieve it for a particular project

Re: Poll: What do you use to track your bugs?

#57
I use http://www.codespaces.com, but I'm biased because I know the guy that founded and still runs it. It was the first app I saw that was fully written in Ext-js (this was pre 1.0) and back in 2007 or whenever it was that he wrote it it blew me away. It does all kinds of neat things, but mostly it's good because it's accessible to non-technical people -- lots of classic interface paradigms.

I also voted for Trac, because that's my go-to bug tracker for corporate projects that get checked in to a private SVN server.

Re: Poll: What do you use to track your bugs?

#58
I use Taskpaper as a task/bug tracking file. Plain text file with GTD token support and line filtering.

Clicking at the beginning of '-' prefixed line will add @done(2011-02-22) and appear as stricken through, and even hidden or moved to the end of the file. I have one per project, and they are tracked with git. Searching for "not @done and not @cancelled" will only leave the tasks remaining to be done.

http://www.hogbaysoftware.com/products/taskpaper

I use an extended DarkMatterPlus* theme file from http://groups.google.com/group/taskpaper/files

* : @fix appear in bright orange, @cancelled behaves the same as @done etc...

Re: Poll: What do you use to track your bugs?

#59
post #51

For those of you who don't know, the OP founded http://bugherd.com/ toast76, can you explain what makes BugHerd unique?

Awesome leading question, thanks!

BugHerd is a tracker for web developers and designers run within the website you're working on. Part feedback tool, part bug tracker, part QA tool. It's a bug tracker that engineers, designers, clients and stakeholders can all use. Each group has a different interface meaning no one is ever in over their head. A lot of the stuff you normally have to enter manually is logged/tracked automagically, meaning more often than not a short description is enough to get all the detail you need to reproduce a problem.

Post reply on HN