views:

97

answers:

2

What Issue Tracking Sytem is the most appropriate for fast, big, multilingual and international websites?

The system has to handle both technical and content/editorial issues.

What's the size and type of your site do you run? Whart System are you using for the keeping it state of the art?

Thanks a lot for sharing your good or bad experience.

+1  A: 

I spend most of my time on the care and maintenance of probably the largest Bugzilla database, with over 3 million rows in its bugs table. Issues in it are described in many different languages, but of course, as soon as you start using UTF-8, that doesn't really matter.

We're using an extensively modified fork of an old Bugzilla version, although I'm working right now on merging our code into Bugzilla 3.6.

I would recommend Bugzilla for your needs, except that you mentioned content/editorial issues. For better or worse, Bugzilla is a bug-tracking system. Things that aren't really bugs in software don't map well into what Bugzilla does well, and Bugzilla doesn't do very well the sorts of things that non-programmers want.

Honestly, I think you should use different systems for what are basically different applications. I don't know what capabilities are important for content/editorial issuer tracking, but I suspect it's different from bug tracking.

David M
A: 

I would use VisionProject. It is a great Issue Tracking Tool and very easy to work with.

MattPro