ticket tracking

jeteve has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: ticket tracking by alexmc (Novice) on Aug 22, 2006 at 10:56 UTC
Have you looked at RT? It is the industry standard as far as I can see. Why dont you want mod_perl or Mason? Can you not install modules?	[reply]
Re^2: ticket tracking by jeteve (Pilgrim) on Aug 22, 2006 at 12:36 UTC
I did, but I can't modify our internal tools server. -- Nice photos of naked perl sources here !	[reply]
Re: ticket tracking by radiantmatrix (Parson) on Aug 22, 2006 at 13:59 UTC
Your question isn't as clear as it might seem. Firstly, what do you mean by "ticket"? Are you looking for a bug, issue, or defect tracking system? Or some other kind of ticket (e.g. change tracking, service orders, etc.)? I assume "should run as CGI" is a result of not being allowed to install Apache modules/etc. on the target server? "should run as... php" doesn't make sense (PHP is like Perl in that it can run either as CGI or using a web server module {i.e. mod_php}). You'll have to come up with a better definition of "simple": do you mean "simple to manage", "simple code", "simple design", "simple to use"? Do you really mean "should rely on MySQL", or do you mean "must be able to use MySQL if it needs a database"? Depending on your answers to these questions, I have a couple of suggestions: Bugzilla - very powerful, proven, out-of-the-box bug and issue tracking system. Eventnum - MySQL's issue tracking product. Trac - source control and issue tracking package. <–radiant.matrix–> A collection of thoughts and links from the minds of geeks The Code that can be seen is not the true Code I haven't found a problem yet that can't be solved by a well-placed trebuchet	[reply]
Re: ticket tracking by perrin (Chancellor) on Aug 22, 2006 at 13:39 UTC
Sounds like Bugzilla to me, although it's far from simple.	[reply]
Re: ticket tracking by neilwatson (Priest) on Aug 22, 2006 at 13:24 UTC
You need to clearly list and prioritize your requirements before you can determine candidate solutions. Neil Watson watson-wilson.ca	[reply]
Re: ticket tracking by jdtoronto (Prior) on Aug 22, 2006 at 15:01 UTC
jeteve, My vote currently is for Eventum. Whilst I wish it were in Perl, it seems to be pretty good quality PHP. There is an active mailing list and ongoing support and development from within MySQL. I use it on Linux (CentOS 4.3), it has a very quick and easy automated installer process and was very fast for people to learn. We have installed it for one client who use it as a 'Feature request' and 'Job Management' system as well as for issue tracking. In six months they have logged about 18,000 issues with bascially no problems. I also looked at Trac (as suggested by radiantmatrix) and whilst the idea of integrating source control is nice, there use of SVN made it troublesome as we are a CVS user (one of my contractors is a CVS maintainer so I am kinda stuck!). Bugzilla is worth a look, it is big, and as Perrin so subtely reminds us, is not simple. But it does work well in places where I have seen it. There are some bugzilla users here in the monastery. jdtoronto	[reply]