[DBTech] DragonByte eCommerce: Tickets 2.2.4

Update highlights

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

Update highlights

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

Update highlights

This update fixes a couple reported bugs with the "default assigned agent" feature.


Complete Change Log

Fix: Allow tickets to be submitted if a default assigned agent is not set
Fix: It is now possible to remove the default assigned agent