* [CHD-3140] [Mail/Quick Search] FIXED: Quick search on a custom 'owner' (worker) field for 'nobody' breaks on ticket worklists.
* [CHD-3139] [Mail/Worklists/Orgs] FIXED: Clicking on '(none)' when subtotaling a ticket worklist by organization doesn't filter to only rows without an organization.
* [Virtual Attendants/Notifications/Usability] In the 'New notification for me' event, the 'Send email to me' action now allows placeholders in the subject field.
* [CHD-3138] [Virtual Attendants/Usability] FIXED: Disabled workers are shown in the 'Add:' fields for watchers and notifications in several Virtual Attendant actions.
* [Code Cleanup/Performance/Parser] Removed an extraneous INNER JOIN between the `message` database table and `ticket` when looking up mail message-id headers in the parser.  This should yield a minor performance improvement. (Thanks to Robert Middleswarth for pointing this out)
* [CHD-3135] [Virtual Attendants/Simulator] The Virtual Attendant simulator will now include closed tickets in the random sample as well.
Merge branch '6.1.3' into 6.2
* [Web-API/Usability] REST API requests can search for multiple values when using OPER_IN/OPER_NIN by encoding the value as a JSON array.  For example: ['option1','option2']
* [Web-API/Usability] Fixed an issue in JSON search results from the Web API.  The results were in an object with the ID as a property key, when they should be returned as an array to preserve the ORDER BY preference.  The properties of objects are not guaranteed to be in any particular order in Javascript, and numeric properties are often sorted in ascending order for performance reasons (especially in Chrome). This meant that in some contexts, the results of a search through the API would provide the proper first page of results, but the order of those items would always be sorted by ID.  This behavior depends on the JSON consumer (e.g. Chrome, NodeJS) and did not affect XML results.
* [Web-API/Usability] Fulltext searching from the Web API will now always be performed in expert mode by default.  A JSON array can be provided to change this behavior, with the first element being a search term, and the second element being one of: any, all, phrase, expert
* [Search/Fulltext] Punctuation will no longer be stripped from the query when performing fulltext searches in expert mode.  This was removing double quotes from phrases and +/- from boolean operators.  This affected the REST-API and the worker GUI.
* [Web-API/Performance] The Web-API will now lazy-load linked records on GET requests and search results when the 'expand' parameter is provided.  This is a comma-delimited list of extra fields to include.  If a field loads another object, all of those fields will be returned as well.  For example, if you want all the associated organization fields to be returned when retrieving a ticket, include 'ticket_org_' in the 'expand' parameter.  The reason this information is not returned by default is because there can be a dozen linked records per result.  It's inefficient to load all this information when it isn't needed, so the 'expand' parameter allows you to specify when you need more info, like custom fields, watchers, etc.
[Code Cleanup] Whitespace
* [Web-API/Workers] The REST API now provides a /workers/me URI (.json or .xml) for retrieving information about the current worker.  This is useful when authenticating with API credentials so the client can be associated with a particular worker record.
* [Code Cleanup/PHP] Fixed some PHP strict mode warnings.
Merge branch '6.1.3' into 6.2
[Code Cleanup] Whitespace fixes
* [CHD-3171] [Mail/Parser/Defunct] The parser will now mark addresses defunct based on an 'Original-Recipient' or 'Final-Recipient' in the message/delivery-status.  Previously it only used the original recipient, which Exchange seems to rarely provide.
[CHD-3156] [Code Cleanup] More PHP STRICT_MODE fixes
[Code Cleanup] Explicit variable declaration