osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now
I hate to say this, but my upgrade to 1.7 was a disaster.
First, I'll be man enough to say that I depended on my servers backups instead of creating one on my own. Huge mistake. In the past, my host (OneWorldHosting) has maintained backups in increments, and per their own website kept backups DAILY, which would have been perfect. But they don't and they didn't and I screwed myself as a result. FAIR WARNING TO US ALL, I guess.
HOWEVER - The 1.7 installation did not do a check on the db to see if it was clean or if it contained populated tables. This should be a required check so that the install and upgrade scripts can treat a db appropriately. I'd also like to point out that the upgrade.php resides in /scp and install.php resides in /setup, which I feel is a flaw that needs to be addressed.
Installation files should all reside in the same directory, and the setup process should include a way to interact with the db and installer to see if the setup is indeed an upgrade or a fresh installation. The upgrade.txt file in the root did not mention an upgrade.php file. I only found it after looking through the directory to see if there was something that I missed...
I guess that's why we're still in RC3 state.