Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

issue tracking vs bug tracking

Stephen Adler wrote:
> Another philosophy question....
> Issue tracking vs bug tracking. I need to set something up and looking 
> through wikipedia, I realized that the two are different, yet sorta the
> same. Should I setup both? What issue trackers have people used, and what
> bug trackers, (besides bugzilla,) have people used?

Bugzilla is industrial strength, but by the same token it's too heavy weight
for my needs.  If you're using subversion, Trac (
) is a nice integrated code browser+wiki+ticket tracker.  It's not that hard
to customize either.  The best part is that you can put wiki links in your
subversion commit messages, and there's a subversion post-commit hook that
lets you update/close Trac tickets with svn commit messages (this is a
killer feature as far as I'm concerned).

I can't see a compelling reason to have separate 'issue' and 'bug' databases
(in Trac, the default classes of ticket are: enhancement, task, and defect).


This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /