* [CHD-3507] [Mail/Reply/Custom Fields] Fixed an issue with setting multiple value custom fields while replying to a ticket.  Previously selected options were being removed without having been explicitly 'unset'.
6.5-release checkpoint
Merge branch '6.5' into stable
* [Virtual Attendants/Simulator/HTTP Requests] When a Virtual Attendant executes an HTTP request as an action, a new "Also execute HTTP request in simulator mode" option is available.  This is useful for testing behaviors when an HTTP request is read-only (e.g. GET), and it's also useful for testing live PUT/POST requests without leaving the simulator.
* [Virtual Attendants/Simulator/Run Behavior] Virtual Attendants using the 'Run behavior' action may now enable an 'Also run behavior in simulator mode' option.  Previously, the simulator only showed that a behavior would have run.  Now delegate behaviors can also run in simulator mode, which makes it much easier to test and troubleshoot complex chained behavior.
* [Virtual Attendants/Scheduled Behavior/Usability] The scheduled behavior popup on profiles now provides enough room for the "When:" text box.  Previously, if the drop down of date fields was very wide then the text box could be compressed to only a few characters.  If the dropdown is exceptionally wide now, the text box will wrap to a new line.
* [Devblocks/Platform/Resources] TTF and WOFF font resources will now be transferred through the resource proxy with the proper mime types.
* [Virtual Attendants] In Virtual Attendant actions, the Virtual Attendant itself will now always appear as a target in the 'On:' parameter.  This happened in some places (e.g. mobile behaviors, API behaviors) but not everywhere else.  This makes it much easier to delegate behaviors between Virtual Attendants using the 'Custom virtual attendant behavior' event.
* [Virtual Attendants/Links] Virtual Attendants can use a new 'Get Links' action to load links of any type on any related record into a variable or placeholder.  For example, when new mail is received a Virtual Attendant could check for a specific type of link (e.g. product, license) on the organization of the message sender.
6.5.1-dev checkpoint
* [CHD-3557] [Workspaces/Dashboards/Subtotals] Fixed a bug where filters with NULL (e.g. blank) values in worklist-based widgets were being ignored in some cases.  For instance, a pie chart showing task assignments based on a worker custom field, with an 'assignee is not blank' filter, would show all workers including 'nobody'.
* [Setup/Branding/Usability] Renamed 'Logo & Title' to 'Branding' in the Setup->Configure menu.
* [Setup/Branding] The favicon used by Cerb is now configurable on the Setup->Configure->Branding page.  Thanks to Niek Beernink @ Oxilion.nl for the contribution!
6.5.1-dev checkpoint
* [CHD-3464] [Consistency] Fixed a consistency issue where the refresh button on some profiles (e.g. task, worker) said "Reload this ticket" in the tooltip.  This was due to the reuse of text from the translation system.  These tooltips now show 'Refresh'.
* [CHD-3561] [Setup/Mail/Filters] Fixed an issue on the Setup->Mail->Filtering page where 'Create behavior' buttons weren't being displayed for each of the Virtual Attendants listed.
* [CHD-3565] [Virtual Attendants/Comments] The 'New comment on a record' event can now use the comment's parent record or author as 'On:' targets for actions.  These were previously ignored because they are abstract (i.e. they can end up being various record types, and it's not possible for the simulator to know in advance).  The author and parent record of a comment still can't be used in the 'On:' parameter of run behavior, schedule behavior, or unschedule behavior actions; instead, the desired record should be loaded into a private variable of a specific type (using {{comment_record_*}} placeholder fields), and that variable can be used as a target.
* [Comments/Worklists/Choosers] Implemented subtotals, filters, and choosers for comment worklists.
* [Worklists/Export] Fixed errors when exporting virtual fields from a worklist.
* [Virtual Attendants/Comments] When simulating new Virtual Attendant behaviors on the 'New comment on a record' event, a specify comment record can now be targeted for testing.  Previously this wasn't possible due to a lack of comment choosers.