osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now
We're designing the beginnings of a plugin architecture for osTicket 1.8. It won't quite make osTicket 1.8.0, but it will definitely be part of osTIcket 1.8.1 later this year. Since I'm overhauling a few components of the system to make them more extensible, I'm interested in hearing your input on what parts of osTicket should be made more pluggable. What types of plugins do you think osTicket should support?
osTicket 1.8.1 will ship with two "classes" of plugins. The first is pluggable authentication, which will enable plugins to extend the authentication mechanism of osTicket beyond the built-in username/password information stored in the staff table. Things like LDAP, Kerberos, Active Directory, RADIUS, Google, and HTTP pass-thru authentication, etc., will all be installable and configurable via plugins.
The second is pluggable attachment storage, which will re-enable storage of attachments on the file system, or perhaps more creative solutions, like using Amazon S3. I'm also interested in writing a archive and retention plugin which will simply integrate with the cron system to retire (delete) or offload attachments by moving them to another storage backend (like from the database to S3).
Another idea I have is to allow a plugin to define email templates and interact with the ticket lifecycle in order to send new ticket alerts or auto-responses, such as the often-requested ticket-closed email.
Yet another idea is to allow plugins to create something like a "widget", which can be configured in the staff or admin panel and shown in the staff or client panels. Some ideas of using the widgets might be like a "message-of-the-day" widget or a clock widget to facilitate time tracking.
Of course, the greatest concerns in the plugin architecture is internationalization and API integration that won't obsolete plugins at the next version of osTicket.
I'm working through the early details of the plugin architecture, and I hope to create something that can retire "mods" and create a new marketplace per se with community plugins available to be installed alongside the stock osTicket. I'd really like to hear your feedback about what things osTicket should be able to do via plugins.