After a lengthy beta period here @ DBTech, v2 of DragonByte Tickets is now ready for release
This version contains one very important feature: Secure Data Storage.
This allows the ticket starter to enter data into fields defined by the admins (using the same feature as Thread Fields / User Fields and every other custom field). Once the user submits the form, a random encryption key is generated and emailed to the assigned agent as well as the user who started the ticket, the data is then encrypted with this key before being inserted into the database.
The data can only be decrypted by entering the secret key (even to the thread starter), and the data (even in its encrypted form) is only ever accessible to the assigned agent and the thread starter. The secret key is then stored in a cookie, which expires at the end of the browser session (when the user closes their browser).
The thread starter or the assigned agent can erase the encrypted data at any time, even if they lose the secret key. The person viewing the secure data can also press a button to hide the data again. No over-the-shoulder snooping
While this system has been tested here @ DBTech, and the most modern (at the time of writing) encryption standards are being applied, it is still advised that you do not use this system for long-term storage of data. Once the ticket has been resolved, it is strongly recommended to click the delete button to erase the data.
This version massively reworks the way support ticket actions are executed. Previously, they would only execute when viewing the ticket, or when the ticket was replied to, or via a cron job. Actions are now executed whenever the ticket is updated, as well as via a cron job.
This, combined with the new ticket criteria for when a ticket's status is being updated, means it's possible to immediately close fully solved tickets and still have features like auto-responders work, without needing to wait for the cron to run.
Complete Change Log
Feature: Ticket actions are now matched / executed whenever the ticket is saved (such as changing the status or reassigning the user) Feature: New action criteria have been added for ticket modification dates Change: Ticket criteria have moved into their own tab in the Edit Actions interface
This update adds the ability to see the ticket status in the thread list, as well as fixing a few bugs reported by the community.
The registration defaults have also been changed, no longer requiring an entirely separate setting. The toggles can be found inside XF's own registrationDefaults setting.
Complete Change Log
Feature: Ticket status is now displayed in the thread list Change: Merged registration defaults into the core setting Fix: Fixed server errors occurring in certain scenarios Fix: On certain systems, the product could fail to install because of MySQL key length limitations Fix: Ensure alerts are tied to addon ID