Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Sun, Oct 22, 2006 at 05:33:07PM -0400, Stephen Adler wrote: <snip> > 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? > > Thanks in advance for the comments. > > Steve. Steve, I think that your developers would tend to appreciate a single system. However, if you have a separate support team, you _might_ want to keep your development tasks away from their eyes. Sometimes someone might tell an outsider about product plans/activities that are best kept quiet. Bugzilla _could_ handle both in a single database if you properly define groups. I'm a big bugzilla fan. I support a number of internal installations where I work. Bill -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |