A video about Trac

[Gebb]

I'm trying to convince my colleagues that Trac as a bugtracker is superior to TFS which we're currently using, and I made this video.

Excuse the high tempo, it was intended to help me conduct a Trac presentation at work at which I was supposed to make pauses and explain things. Just thought I might share it with you.

[Voelker, Bernhard]

Gebb wrote:

> I'm trying to convince my colleagues that Trac as a bugtracker is
> superior to TFS which we're currently using, and I made this video

> <http://www.youtube.com/watch?v=g0RONl7LtH4> .

> Excuse the high tempo, it was intended to help me conduct a Trac
> presentation at work at which I was supposed to make pauses and
> explain things. Just thought I might share it with you.

Thanks!

Have a nice day,
Berny

[W. Martin Borgert]

Quoting Gebb <otto...@gmail.com>:
> I'm trying to convince my colleagues that Trac as a bugtracker is superior
> to TFS which we're currently using, and I made this

> video<http://www.youtube.com/watch?v=g0RONl7LtH4>

Very nice video, many thanks for sharing!

I don't know TFS. Can you (or somebody else) explain
how it compares to Trac?

It is a little bit unfair to let Trac go unarmed into
the "battle". I would suggest to let it use at least
these two tools of the Trac swiss army knife:

1. The WYSIWYG plugin should be installed. Managers
love it. And it's great for editing tables.

2. CI: You should show Bitten to demonstrate, that
any code committed, can automatically be linted,
unit-tested, compiled, and even deployed.

Cheers

[Gebb]

Thanks for the suggestions! I didn't even know about the WYSIWYG plugin.

And I've never tried to integrate Trac with CI, but I will investigate that.

I don't know TFS. Can you (or somebody else) explain how it compares to Trac?

Trac beats TFS even out of the box.

Features of Trac TFS doesn't have:

• wiki;
• ticket description formatting;
• inserting images in the description;
• convenient UI (you have to switch between pages to see attachments or the owner/assignee);
• ticket linking capabilities: in TFS you go to a separate tab and add a ticket to the list visible only from that tab, you can not insert a link in the ticket description;
• source control integration;
• text search in comments.

Features of TFS Trac doesn't have:

• time management;
• Visual Studio integration (I don't know why some guys like that).

I haven't tried Trac's time management plugins and don't know how good they are but I know there are some.

[stevecel]

For us that work with Microsoft technologies, the Visual Studio integration is quite important, but that is mostly for Subversion stuff. There are excellent tools out there that do Subversion integration in Visual Studio:

• VisualSVN [http://www.visualsvn.com/visualsvn/] (Commercial)
• AnkhSVN [http://ankhsvn.open.collab.net] (Free)

There once was a decent attempt on making a Visual Studio integration for tickets and wiki pages too, but the project kind of died:

http://sourceforge.net/apps/trac/vstrac/

If you want a fat client for working with tickets, you could have a look at http://www.fat-bug.com/ (commercial).

[W. Martin Borgert]

On 2012-02-08 23:24, Gebb wrote:
> Features of TFS Trac doesn't have:
>

> - time management,

This is something very difficult, independent of the tool one
uses :~) I have never tried this, but one could maybe combine
the following plugins:

- TimingAndEstimationPlugin (for estimated and total hours)
- MasterTicketsPlugin (for dependencies)
- SubticketsPlugin (for parent/child relationships)
- TracJsGanttPlugin (for graphical display)

If you ever make use of this, please make a video! :~)

> - Visual Studio integration (I don't know why some guys like that).

There is VsTracIntegration, but from its description it looks
more like an SVN than a Trac integration, and you seem to use Hg
anyway.