[DBTech] DragonByte Tickets 4.2.0

Update highlights​

This version improves the workflow for support agents by adding a checkbox that automatically updates the status to "Answered" when replying. Furthermore, an activity log has been added, locked behind a new user group permission.

Lastly, a bug has been fixed that would prevent the first ever ticket in a new support forum from posting correctly if the "Quick Thread" interface was used.

Complete Change Log​

Feature: Support agents can mark a ticket as answered when replying
Feature: New ticket activity log recording status and assignment changes, viewable with the new "Can view action log" permission
Fix: Creating a ticket via the quick thread form in an empty category now shows the new ticket instead of appearing to do nothing

Update highlights​

This version adds "Availability hours" and "Out of office" functionality to the Preferences page of users with a new "Is support agent" permission. Once configured, the availability hours can be utilised via new Action criteria, to create automated messages for when tickets are posted outside of the assigned user's available hours (or while the agent is out of the office).

The "Availability hours" is designed explicitly for use with the Actions, whereas the "Out of office" feature displays a notice box on top of the ticket stating the agent is out of the office (with the start and end dates), and displaying the message the agent left (if any).

In addition, a bug has been resolved that could cause ticket actions that trigger on ticket creation, to trigger multiple times in succession. This would also occur if you had multiple actions that would run on creation, but you relied on "thread has no more than 0 replies" as a criteria to stop multiple bot responses.

Complete Change Log​

Feature: New "Is support agent" permission. Support agents can set their weekly availability hours in their account preferences
Feature: New ticket action criterion: ticket was started outside the assigned user's availability hours
Feature: New action message variables {availability_start}, {availability_end} and {timezone}
Feature: Support agents can set an out of office period and message, which is shown on tickets assigned to them
Feature: New ticket action criterion: assigned user is currently out of the office
Feature: New action message variables {out_of_office_start_date}, {out_of_office_end_date} and {out_of_office_message}
Fix: Fix ticket actions running more than once when a new ticket is created, which could post duplicate automated replies

Update highlights​

DragonByte Tickets no longer requires DragonByte eCommerce!

That's right, you can now use DragonByte Tickets as a completely stand-alone ticket system, without needing DragonByte eCommerce!

This version fixes a few issues reported during the Beta period, as well as making additional fixes to the integrity of the "Secure data" encryption feature. A few other minor issues have been discovered and corrected, please see the full changelog for details.

Complete Change Log​

Fix: Remove the possibility for a server error to occur if 3rd parties integrate with Tickets
Fix: Fix a server error on Overview pages if the support category had no valid child nodes
Fix: Fix stuck job if no cron-executable actions exist
Fix: "Receive emails for ticket replies" registration value setting is now preserved on upgrade from v3
Fix: Fix user ticket count function not returning the correct value
Fix: Fix ticket stats collection
Fix: Fix ticket field phrases using the old values when entering secure data
Fix: Encrypted ticket fields can no longer be emptied on edit

Update highlights​

This product no longer requires DragonByte eCommerce!

That's right, you can now use DragonByte Tickets as a completely stand-alone ticket system, without needing DragonByte eCommerce!

This version adds a new link in the navbar that lets you quickly see unanswered support tickets.

Furthermore, a cleanup pass has been done on the uninstaller - Thread and Forum Types are now cleaned up on uninstall as they should have been. The upgrade step also cleans up a remnant that would have been left over if you had first installed v3, then upgraded to v4, then uninstalled, then reinstalled v4.

Complete Change Log​

Feature: "Unanswered tickets" link in the navbar, and in the filtering
Fix: Clean up thread types/forum types on uninstall
Fix: Clean up leftover Suggestions forum/thread type if v3 was uninstalled and v4 reinstalled

This add-on has been hotfixed to address an issue affecting all front-end pages while this add-on is enabled. This issue was caused by additional security measures introduced in XenForo 2.3.13.

The latest version has been patched, and can be downloaded at no additional cost. If you are running an older version and you are unable to upgrade for whatever reason, please let me know the exact version you are running and I will apply the hotfix accordingly.

Note: Both the latest Beta version and the latest Stable version of this add-on has been hotfixed.

Update highlights​

This product no longer requires DragonByte eCommerce!

That's right, you can now use DragonByte Tickets as a completely stand-alone ticket system, without needing DragonByte eCommerce!

The "eCommerce product suggestion" forum type has been moved to DragonByte eCommerce, and so have all references to products and licenses. As a result, both the product itself and the text/internals of the addon have been renamed to drop all mentions of "eCommerce"!

If you use both eCommerce and Tickets, I would strongly recommend upgrading eCommerce to v5.3 alongside upgrading Tickets to v4 to avoid any unforeseen issues. The upgrade should be safe, as I have already upgraded both addons @ my website with no data loss

The only other change is adding a couple of widget positions that had references in the templates but not actually being wired up to anything. Whoops.

All other changes are internal/developer changes that should not affect usability.

Complete Change Log​

Feature: No longer dependent on DragonByte eCommerce
Feature: Add widget positions for Ticket Category and Ticket Overview pages
Change: Rename code events and fix developer docs
Change: Move "Product Suggestions" and "Add to order" features to extensions within eCommerce
Change: Rename the Ticket thread and forum types
Change: Remove product-specific phrases
Fix: Remove unused phrases
Fix: Properly clean up ticket field phrases on uninstall
Fix: Fix navigation permission check during addon upgrade

Update highlights​

This version improves compatibility with future versions of XenForo by moving certain code calls out of templates. This update is recommended to avoid compatibility issues with the upcoming XenForo v2.3.8 & newer.

Furthermore, a performance tuning pass has been completed on the Ticket Action edit page, to reduce query count.

Complete Change Log​

Change: Move database query calls from templates to PHP files
Fix: Reduced query count for the Ticket Action edit page

Update highlights​

This version contains internal changes to be compatible with the upcoming XenForo v2.3.8.

Furthermore, leftover jQuery code has been replaced.

Complete Change Log​

Change: XenForo 2.3.8 compatibility
Fix: Fix leftover jQuery code

Update highlights​

This version updates the Open Support Tickets widget, pre-fetching more data and eliminating multiple queries per widget.

Complete Change Log​

Fix: Reduce the query count for widgets

Update highlights​

This version fixes a couple issues, see the changelog for the full details.

Complete Change Log​

Fix: Moving a thread into a eCommerce Ticket Support node could produce a server error
Fix: Don't double-escape the cost description