2.0.3

Release Details

Important Notes

• Enable SSL option enforced everywhere - If SSL is enabled in the general settings, it will now only allow access via HTTPS for the frontend, operator panel and API, with an automatic redirect if you access the frontend or operator panel via HTTP. Therefore the 'force SSL for operators' option has been removed as this is now automatic. If you are using the API or WHMCS integration, please ensure to use the secure version of your website for the system URL for it to continue working as normal.
• System URL used more consistently in emails - The system URL (set in general settings) is now more consistently used when sending emails to users and operators. Please ensure this is set correctly and make sure to update if you change your domain in the future.
• Trusted hosts - To prevent unvalidated redirects when logging in to the frontend and operator panels, we have implemented a trusted hosts list. By default, only the same host as you're logging in to is permitted. Please read adding trusted hosts, for more information.

Notable Changes

• Ticket view changes - Due to performance issues when loading tickets containing several larges messages, several changes have been made to the frontend and operator ticket view. For details on tuning this functionality, please read App Configuration.
  1. Messages that are greater than 102KiB are now loaded on demand via AJAX.
  2. Messages that are greater than 102KiB that are not loaded via AJAX are now clipped. A "View entire message" link is appended to bottom of the message which loads the message in a new window.
• Improved canned response searching - The add canned response popup in the ticket view has been completely redesigned to make searching for a response easier and more useful. Up to 10 commonly used or recent responses are shown by default and ordered by your own choice. Tags can also be assigned to canned responses, and can be used when searching for responses. Canned responses can now also be added when opening a new ticket, but the use of ticket merge fields will provide blank values.
• Default reply options - You can now personally select what reply options are and aren't selected by default when responding to a ticket. The option is available under the Ticket Settings tab in your personal settings.
• Turn off notifications for organisation managers - Some organisation managers may wish to not be emailed about updates on other organisation user's tickets. A global option has been added to the User General Settings to set a default, and an option also exists in the profile for each user (that is a manager of an organisation). The manager can also choose their preference in their profile in the frontend.
• Mass email improvements - The option to email all users and add attachments has been added to mass emails. It will now also show an estimated time to send all emails.
• Separated permissions for managing users and operators - Previously managing operators was covered by the managing user permissions, it now has it's own permission and can be disabled for certain roles.
• Save notes on users - It's now possible to save operator-only notes for each user in their profile.
• Update ticket custom field value action - An action has been added that allows the updating of a custom field value on a ticket. This action can be used in follow ups, macros and SLA escalation rules.
• Ticket grid default direction - It's now possible to show results ascending or descending by default.
• Disable organisations - If you only deal with consumers, you may not need to show the organisation option on the frontend to your users. A setting has been added to User General Settings -> Organisations that will completely hide it from the interface and stop all functionality related to organisations.

Resource Changes

Many of the changes in the links below are switching from using the asset function to asset_rev for our asset files, a custom function which appends the version number to the file URL. This means files are always fetched fresh when upgrading to a new version, as cached files can commonly affect functionality.

• Language file changes (from 2.0.2)
• Frontend template changes (from 2.0.2)
• Operator template changes (from 2.0.2)

Changelog