A few years back we selected FogBugz ( as the best issue tracking system available. It integrates well with versioning systems, has an integrated wiki and project management abilities. We are very satisfied. It is not an open source product however, but not extremely expensive.


      Drs. P.J.C. van Boheemen
      Business IT consultant Library and Search
      FB - IT - Wageningen UR
      tel. +31 317 48 25 17  

-----Original Message-----
From: Code for Libraries [mailto:[log in to unmask]] On Behalf Of Jonathan Rochkind
Sent: woensdag 22 februari 2012 23:18
To: [log in to unmask]
Subject: Re: [CODE4LIB] Issue Tracker Recommendations

On 2/22/2012 5:10 PM, Sebastian Karcher wrote:
> Because Trac and Git have come up: Zotero has switched from Trac/SVN 
> to Git and I (and I think everyone else involved) much prefers git, 
> not least because of it's better issue handling. I found Trac slow, 
> clumsy, and ugly.

I'm confused. Git is a source control repo, like svn.

Trac is an issue tracker.

Okay, you switched from svn to git (which to me seems somewhat orthogonal to issue tracker, although it's true that certain issue tracker software integrates with some versioning control systems and not others, like trac does with svn).

But what are you using for issue tracking now, instead of Trac?  git is not an issue tracker, so I'm not sure what you mean by "git's better issue handling", git doesn't do issue handling (any more than svn does). 
Do you mean you're using as your git host, and their issue tracker? Or something else?


> If, as you say, the code repository function isn't important, there 
> may very well be better products for issue tracking only, but between 
> Trac and github the latter is imho much superior.
> On Wed, Feb 22, 2012 at 1:52 PM, Sarr, Nathan 
> <[log in to unmask]>  wrote:
>> You might want to take a look at asana:
>> -Nate
>> Nathan Sarr
>> Senior Software Engineer
>> River Campus Libraries
>> University of Rochester
>> Rochester, NY  14627
>> (585) 275-0692
>> [log in to unmask]
>> -----Original Message-----
>> From: Code for Libraries [mailto:[log in to unmask]] On Behalf 
>> Of Cynthia Ng
>> Sent: Wednesday, February 22, 2012 3:46 PM
>> To: [log in to unmask]
>> Subject: Re: [CODE4LIB] Issue Tracker Recommendations
>> Thanks for all the responses, everyone. If there are any more, I'd still like to hear them.
>> Should probably add that
>> 4) it's more for issue tracking/documentation i.e. code 
>> versioning/repository is not a priority right now (though it's great 
>> if it has that feature)
>> There will be discussions with the rest of the team and we'll have to talk to the programmer/server admin to see what he thinks is easier to implement, but we're likely to go with Redmine or Trac based on recommendations/needs.