Double Choco Latte or Request Tracker

After hundreds of unarchived troubleshooting effort, I felt that I needed a method to keep those records logged. This idea brought me into this solution: trouble ticketing system. I liked the idea of having all the troubleshooting progress monitored and logged, simply by entering the information from web.

Crawling the web for any related open source project brought me some...well, actualy plenty of choices:

• Bluetail Ticket Tracker (BTT)
• Bugin
• Bugzilla
• Double Choco Latte (DCL)
  
• GNATS (aka PRMS)
• HelpDesk
• JitterBug
• Job Control System (JCS)
• OpenTicket
• Open Track
• PHP HelpDesk
• PHPSAT
• ProManager
• Request Tracker (RT)
• ReqNG
• Roundup
• Scarab
• Teacup
• TouxDoux
• WebCall
• WHUPS
• wreq

Quick look at my Ubuntu repositories reduced them to two: DCL & RT

So, it was the time to choose........hmm..............nevermind, I just picked both.

Being quite a coffee geek, I went first with DCL. After wrestling with postgresql, and set it up, I felt that this animal was so buggy and relatively unmaintained that I had to abandon it.

The setup of RT was done somewhat easier, as its documentation spread over the web. I felt that RT was much more mature since it had been around for longer period. However, I felt the administration was a bit kludgy. I also disliked the user interface style. Rather than customizing it, I decided to continue my journey in searching trouble ticketing system apropriate to my work.

So...here I am....
Back with manualy logged troubleshooting,.... with pen and papers scattered troughout my desk.
ROFLMAO