Jared,
I am setting up Ozticket on my website as a strategic move from comm100 that I have used for many years . I am using ozticket 7.2 and I find I need the following :
Time tracking and reporting
Time Scheduling ( to age and monitor Ticket / Staff performance by time as in "Auto update " and " Auto Follow-up " based on time)
More flexiblity with the SLA setup
Ability to add additional Drop-downs
Merge Tickets
Batch Assign ( and Delete )
Next / Prev ticket buttons
Duplicate ticket warning
Reporting similar to "Scottro's Reporting mod " ( which is a very close replication for comm100's )
then, as ntozier indicates,
DB Cleanup tools
Followup / Customer Rating system
Here I need to say it would be nice if we could settle down to some ( limited ? ) structure / coding standardization as the way forward. I am finding that the majority of the wishlist above are catered for in the mods but for lower versions with the corresponding files obsoleted in 7,2 .
Example is the infamous "viewticket.inc.php" that is used in many mods.
Further reflection, what would be really great is to do as zencart does,
a) a link from the scp / admin panel to the ozticket homepage / forum / mods section
b) a "Developers Tool Kit" section to find specific code
c) a " install SQL Patches" section for SQL mods
d) a Section in the ozticket forum where all the mods are packed for ease of installation, each mod has its own section with upgrades, comments, developer etc