[lug] Request/bug tracking systems--suggestions for small team
Vince Dean
vdean at ucar.edu
Fri Feb 15 13:50:13 MST 2008
Our small software team needs some sort of bug/request
tracking system.
This is a small, in-house team of 3 developers who would be
the main users of the system. We could almost get away with
a spreadsheet to track and prioritize our tasks, but we need
something that is easily shared among us, probably web-based.
It needs to be free, and relatively easy to install and
administer.
This does not need to be be usable by a larger user community.
Some reports might be useful for our managers, but this is
secondary. We mostly need to manage priorities among ourselves
and make sure issues are not forgotten. We need to
track the basic facts about a task: priority, status, description,
assigned-to, subsystem, etc., with reports sorted by those
attributes.
We don't require close linkage to the source code. We don't
necessarily need to associate a request with the code changes
it caused.
When we needed source control, Subversion was an obvious choice:
widely used, free, well-respected, all the features we might
need, but not too hard to use. A "safe" consensus choice.
Are there any equally obvious choices for request tracking?
One suggestion is Trac. Would that meet my requirement for
a well-established, versatile and relatively light-weight
system? I understand it can be closely integrated with
Subversion.
Our administrators use WREQ to track trouble tickets. I'm not sure
that's what we need, because I have a hunch that tracking system
administration requests is not quite the same as tracking software
bug/feature requests, but I can't say why.
Suggestions?
Thanks,
Vince
--
Vince Dean
SIPS Operations Manager - Center for Limb Atmospheric Sounding
HIRDLS Program
University of Colorado at Boulder
3450 Mitchell Lane, Bldg. FL-0
Boulder, CO 80301
Phone: (303) 497-8077
More information about the LUG
mailing list