Work on hclTicket 0.0.1 is coming along. This version is basically you can enter a ticket and get it back out. It nearly has NONE of the features that Tommyjohn has suggested
This one actually is getting a lot of work, because I want something stable with as few bugs and security holes as possible. Every change gets uploaded to a web server and tested. This is not normally how I program. I normally write for a few hours then upload when routines are considered done, that's the fast way. However with all of the headaches on the other ticket systems, I want this one solid.
I had to make the decision to abandon eTicket/osTicket. I just don't see either one as viable. osTicket is dead. eTicket has a long way to go for stability under HCL, it would amount to a fork of the system. I just don't see the point, as eTicket has a lot of replication of functions. We really don't need it to have a login, cached output, etc. HCL provides a wealth of functions that are available to every module, it makes no sense to waste those resources. So if I am going to put 30 or 40 hours into a trouble ticket system, I'm going to do the one that makes the best use of resources.
I'll update this topic as we progress. I'd like to have 0.0.1 before the end of the month. At that point we can start adding features, and start getting to where 2.2.0 will require it to be (2.2.0 has a LOT of changes, in particular the way modules are handled.)
update 6/28/07 04:00a MST: After 3 hours of chunking out code and basically making wrappers, I deleted all of the PHPticket I was was using as a template. Making another ticket system conform just isn't efficient and frankly, it's faster to code by hand. Right now I've got the guest template done. I've built the add ticket function, and can list the tickets. That's in an hour and a half. I should have the module working and in alpha by Friday. One thing, we noticed yesterday that there is a form buried in the HelpCenter Core module. That has just got to go, as it breaks this module, and makes templating a nightmare. So 2.1.3 is going to be getting one last (hopefully) fix and then we should be good to go. What this also means is that version 2.1.2 will need a hotfix to run hclTicket. However I don't see that as a major thing, the change affects 3 or 4 files, only one of which is PHP.