[Trac] Trac VS Bugzilla

[normalAnomaly]

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.

[yoheeb]

for lack of a better summary, comparatively, bugzilla sucks. But that
is truly an opinion. I have found trac significantly more capable,
more flexible, and easier to tweak. However, I never have liked
bugzilla, so I am biased. The customizable work flow, combined with
the typedTicketWorkflow plugin, just allow me to do things I counld
never make happen in bugzilla. combined with other little things,
like ticketValidator plugin, etc. Not to mention the powerful wiki.

The flip side, bugzilla has been around a long time, and has a few
things out there Trac might not. I have no idea what bugzilla is
actually built upon, but Trac was built upon a very well planned and
executed architecture, which sits upon the best language out there for
ease and flexibility of these sorts of things. Again, pure opinion.
I also have found the community superior, not quite sure why that one
is, I could be an anomaly on that one, I just didn't get much help
from the bugzilla community in my limited attempts. Not enough data
to state that as a definitive.

[Roger Oberholtzer]

On Wed, 2009-07-01 at 12:28 -0700, yoheeb wrote:
> On Jun 30, 8:11 am, normalAnomaly <nir...@thenationtraffic.com> 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.

[Иван Бессарабов]

I've had a task - every morning I needed to send list of task to the owners of that tikets.

I've written the small script in perl language. The script is avaliable in my blog, but the blog is in russian language http://blog.bessarabov.ru/2008/07/23/send-active-trac-tickets-to-mail/

I've placed that script into the crontab.

Feel free to contact me on any questions about this script.

2009/7/2 Roger Oberholtzer <roger.ob...@gmail.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?

--
bessarabov

[Óscar Palacios]

I worked with bugzilla for some time and loved it. We used subversion
and bugzilla. I remember the excitement we felt at subversion being the
right answer to a bunch of coordination issues. But when we realized
trac was also a subversion repository web interface (plus a wiki), we
switched. We now use the svn-trac combo for every project.

Óscar Palacios
Mexico City

[Иван Бессарабов]

Are you using different trac for every project or you are using one trac for all your projects?

2009/7/2 Óscar Palacios <oscarpa...@gmail.com>

We now use the svn-trac combo for every project.

--
bessarabov

[Roger Oberholtzer]

On Thu, 2009-07-02 at 10:42 +0400, Иван Бессарабов wrote:
> I've had a task - every morning I needed to send list of task to the
> owners of that tikets.
>
> I've written the small script in perl language. The script is
> avaliable in my blog, but the blog is in russian language
> http://blog.bessarabov.ru/2008/07/23/send-active-trac-tickets-to-mail/

Interesting. What I would like is to send a message to a ticket owner if
the ticket is in a certain status for a certain amount of time. So I
would need to get these things from the ticket:

owner
owner's e-mail address
current ticket status
when the status was set to this
last time the owner modified the ticket

based on that, perhaps I could do something similar to your script. I
guess the main thing is to make the SQL query. I bet there is
documentation on how one gets these things.

[Иван Бессарабов]

The things you are writing can be easily coded, but I'm not the person who will do this task for you =)

Maybe the best way of solving your case is to find the programmer who will do such a thing (actually the task is very simple)

2009/7/2 Roger Oberholtzer <roger.ob...@gmail.com>

--
bessarabov

[Tomek Grzechowski [k3o]]

2009/7/2 Иван Бессарабов <iv...@bessarabov.ru>:

Dont know bessarabov, but we use different trac for every project.

I think they do same. It is more clear/clean.

Of course depends on project size.

--
Tomek Grzechowski
-----------------
miniman@k3o; developer/programmer; http://k3o.eu
minim...@gmail.com; +48 662 279 869 (cell)
skype: miniman.k3o

[Иван Бессарабов]

Yes, I'm also using serveal tracs for big projects and one trac for tiny projects. But this is not very good solution - sometimes the small project gets bigger and it should be moved to the new trac.

2009/7/2 Tomek Grzechowski [k3o] <minim...@gmail.com>

--
bessarabov

[Tomek Grzechowski [k3o]]

2009/7/2 Иван Бессарабов <iv...@bessarabov.ru>:

> Yes, I'm also using serveal tracs for big projects and one trac for tiny
> projects. But this is not very good solution - sometimes the small project gets bigger and it should be moved to the new trac.

Exactly . trac shall be configured for single project.

Its power is simplicity.

[Roger Oberholtzer]

On Thu, 2009-07-02 at 13:32 +0400, Иван Бессарабов wrote:
>
>
> The things you are writing can be easily coded, but I'm not the person
> who will do this task for you =)

I was not hinting that you should do it. I was more thinking aloud - but
in writing. I am happy to extend this myself. I was happy with the info
you provided that got me started.

[Eirik Schwenke]

Иван Бессарабов skrev 02. juli 2009 08:42:
> I've had a task - every morning I needed to send list of task to the owners
> of that tikets.
>
> I've written the small script in perl language. The script is avaliable in
> my blog, but the blog is in russian language
> http://blog.bessarabov.ru/2008/07/23/send-active-trac-tickets-to-mail/
>
> I've placed that script into the crontab.
>
> Feel free to contact me on any questions about this script.
>

I made a minor change, and translated the comments to English (I hope, I
don't speak russian ;-). Just in case it's usefull for someone on this list.

I tested the script briefly, and it appears to work correctly.

Best regards,

--
.---. Eirik Schwenke <eirik.s...@nsd.uib.no>
( NSD ) Harald Hårfagresgate 29 Rom 150
'---' N-5007 Bergen tlf: (555) 889 13

GPG-key at pgp.mit.edu Id 0x8AA3392C

[Иван Бессарабов]

I'm very happy that my script is usefull not only for me

Thank you for the translation! Next time when I write some small progs
for trac I will make the comments in english.

=)

2009/7/5 Eirik Schwenke <eirik.s...@nsd.uib.no>:

--
bessarabov

[Olemis Lang]

On Tue, Jun 30, 2009 at 8:11 AM,
normalAnomaly<nir...@thenationtraffic.com> 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?
>

I see Trac like a big mountain of French chocolate ... Bugzilla is a
skary animal !

Beyond that, I like Trac because customization is very easy, and
everything is well organized, fast dev & tons of incredible plugins.

--
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

[yoheeb]

I forgot a feature a big feature that I use all the time. I use it so
much, I forgot about it.

unfortunately for us, most of out outside contractors, don't have
access to our Trac, and more importantly, our Subversion repo, due to
"IT restrictions" lets say.

So, we end up doing "manual" source control for these individuals.
They send us their changes, we merge them into the trunk, and send out
a zip file of the latest/greatest trunk to everyone. Well, that was
without trac. Now, we still have to merge their changes to the
trunk. but we then go to the revision log for the trunk between
revision LAST_TIME_WE_SENT_IT_OUT and the head revision we just merged
in. we click the "zip archive" download in other formats option, and
send the resulting zip file to everyone, which contains the complete
contents, and directory structure of ONLY the changed files. SOO much
better than doing a full checkout/local copy update, manually zipping
the whole dang solution, and emailing the whole thing (or ftp server,
whatever) Yes, Ideally they would have access to the repo, however my
expectation is that our IT will let that happen in about a billion
years from now....

It's another one of "the little things" that make Trac, as a whole, a
much superior tool. It's not just one or two key features, but its
more than a sum of its parts, significantly more.