Thanks to everyone who responded. The comments have been very helpful!
Is anyone using RT? 
Also, I'm curious how many academic libraries are following a formal change management process?
By that, I mean: Do you maintain a strict separation between developers and operations staff (the people who put the changes into production)? And do you have something like a Change Advisory Board that reviews changes before they can be put into production?
Just as background to these questions:
We've been asked to come-up with a change management procedure/system for a variety of academic technology groups here that have not previously had such (at least nothing formal). But find the process that the "business" (i.e., PeopleSoft ) folks here follow to be a bit too elaborate for our purposes. They use Remedy.
Library Web Services Manager
California State University
From: Code for Libraries [[log in to unmask]] On Behalf Of Mark A. Matienzo [[log in to unmask]]
Sent: Thursday, February 11, 2010 5:47 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] change management system
I'm inclined to say that any sort of tracking software could be used
for this - it's mostly an issue of creating sticking with policy
decisions about what the various workflow states are, how things
become triaged, etc. I believe if you define that up front, you could
find Trac or any other tracking/issue system adaptable to what you
want to do.
Mark A. Matienzo
Digital Archivist, Manuscripts and Archives
Yale University Library