From owner-freebsd-questions Thu May 30 9: 5:39 2002 Delivered-To: freebsd-questions@freebsd.org Received: from cs.selu.edu (cs.selu.edu [147.174.59.5]) by hub.freebsd.org (Postfix) with ESMTP id 66D5B37B403 for ; Thu, 30 May 2002 09:05:32 -0700 (PDT) Received: from localhost (jholland@localhost) by cs.selu.edu (8.11.6/8.11.2) with ESMTP id g4UG5SG08786; Thu, 30 May 2002 11:05:28 -0500 Date: Thu, 30 May 2002 11:05:28 -0500 (CDT) From: Jason P Holland To: Lord Raiden Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Trouble Ticket Tracking?? In-Reply-To: <4.2.0.58.20020528112651.009569e0@pop.netzero.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i use Request Tracker. http://bestpractical.com/rt/ its perl based, has a decent web interface, db backend, access control, lots of other features. jason > Hi all. I'm going to be needing to start a ticket tracking system here > soon so we can track all of the requests for changes to the IS cluster, > results, if it was resolved, repairs to computers, the networks, etc. Our > network is getting big enough now that I need a pro-active way to track all > changes and updates to the network much better than my current system. > > Anyone got any good suggestions? > - The Raiden Knows > > "Remember amateurs built the ark -- professionals built the Titanic." - > Unknown > > "Just when you think you have life figured out and all is going well, watch > your step, for you are about to fall." - Ancient Proverb > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message