On Wed, 2009-07-01 at 12:28 -0700, yoheeb wrote: > On Jun 30, 8:11 am, normalAnomaly <[email protected]> wrote: > > Hello. > > > > I am considering using Trac as an issue and bug tracking system. I've never > > used it before, however I do have some experience with Bugzilla. > > > > Can anyone give me a general overview of pros / cons of using Trac for bug > > tracking over Bugzilla? > > > > Thanks! > > -- > > View this message in > > context:http://www.nabble.com/Trac-VS-Bugzilla-tp24271628p24271628.html > > Sent from the Trac Users mailing list archive at Nabble.com.
I would say that the main thing bugzilla has that I miss in trac is the cron ability. It checks for things that have not been dealt with and sends a message to the concerned party until they do something. Maybe there is a plugin I have missed? Still, we run both trac and bugzilla. We use trac for any change to our product (software and hardware). We use bugzilla for problem reports. Bugzilla is meant to be external, and does not always involve a change in our product. If the bugzilla work decides a change is needed, it is sent to trac. "On TRAC" is a bugzilla state for us. One main reason for this is that we want to treat these two activities separately. Also, we use bugzilla with people who are external to our organization. So, the cron reminders are nice. And, the software development discussions in trac are not always something we want generally seen. Proprietary info and all that. We have invested much more time in trac. So, we may set up the stuff in bugzilla as a new trac project, and then do all in trac. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
