From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.90.79.9 with SMTP id c9cs39904agb; Tue, 3 Nov 2009 09:51:13 -0800 (PST) Received: by 10.224.65.40 with SMTP id g40mr146620qai.333.1257270673363; Tue, 03 Nov 2009 09:51:13 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id 29si438762qyk.32.2009.11.03.09.51.13; Tue, 03 Nov 2009 09:51:13 -0800 (PST) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 116F41598091; Tue, 3 Nov 2009 12:51:13 -0500 (EST) X-Greylist: delayed 2707 seconds by postgrey-1.31 at rubycentral.org; Tue, 03 Nov 2009 12:48:42 EST Received: from hrndva-omtalb.mail.rr.com (hrndva-omtalb.mail.rr.com [71.74.56.122]) by rubyforge.org (Postfix) with ESMTP id 2DBFA1598088 for ; Tue, 3 Nov 2009 12:48:44 -0500 (EST) Received: from daemianmack.com ([72.230.115.149]) by hrndva-comm-mta03.mail.rr.com with SMTP id <20091103170333914.HEBK18643@hrndva-comm-mta03.mail.rr.com> for ; Tue, 3 Nov 2009 17:03:33 +0000 Received: by daemianmack.com (nbSMTP-1.00) for uid 1000 daemianmack@gmail.com; Tue, 3 Nov 2009 12:03:38 -0500 (EST) From: Daemian Mack To: sup-talk In-reply-to: <20091103162047.GD2963@pineapple.q.wohnheim-jahnplatz.de> References: <1257111816-sup-4397@peray> <1257169654-sup-6224@masanjin.net> <02055f053011496a2dcb9085b7e7535f@localhost> <1257261315-sup-977@masanjin.net> <20091103162047.GD2963@pineapple.q.wohnheim-jahnplatz.de> Date: Tue, 03 Nov 2009 12:03:38 -0500 Message-Id: <1257266599-sup-1535@lenin> User-Agent: Sup/git Subject: Re: [sup-talk] Choosing a bug tracker for Sup X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Sebastian Schwarz's message of Tue Nov 03 11:20:47 -0500 2009: > > RT doesn't come with a formal, formatted users or administrators > > guide, but it's likely most of what you need to know to use and run it > > is contained somewhere within this wiki, so look around a little, be > > patient... and try not to install RT on a Sunday night when you need > > to run it in production on Monday: it's big, and learning how to set > > it up can take some time. > > Can anyone with more experience with RT comment on this? Having evaluated RT3 for fairly-intense production use at a prior job, I can't really say I'd recommend it for our use here. As an 'enterprise-ready' solution, it's a bit ungainly out of the box, and the bulk of its feature-set would probably be overkill for sup's needs. It makes heavy use of the 'departmental queue' model whereby many departments, consisting each of many employees, have some permission set for many queues. Customization was a bit opaque (though perhaps less so if you're very familiar with Perl), and though there's an O'Reilly book for RT, I found it often fell short of my needs. I'd suspect, with the glut of ticket-tracker software available, there's something a good deal better-suited for sup out there. I'll chime in again if I manage to find something that seems helpful. -- http://daemianmack.com/ _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk