Let textarea widgets parse and clean input based on configured text format.
Add cleanup routine to ThreadEntryBody
Clean response/note inputs

Conflicts:

	include/class.forms.php
	include/class.ticket.php

This changes the storage model for datetime fields and stores them in the
same format as the MySQL `datetime` column type. This allows for the
searching code to be consistent when searching the database for
datetime custom form entry data.

This changes the typeahead to redirect directly from the typeahead click
rather than redirecting after performing the search a second time on the
ticket queue page.

Let textarea widgets parse and clean input based on configured text format.
Add cleanup routine to ThreadEntryBody
Clean response/note inputs

Also, apply requested state to the user and organization tickets search.

Add ticket count to page bottom. Team-assigned tickets show up in "My
Tickets"

Redirect to recent queue / listing on transfer or assign

- Adds mass assign, transfer to ticket queues
- Retire inline forms for ticket assignment and transfer

Reset permissions and change primary department and role

Fixes #2143

This adds the concept of independent multi-thread rendering

This is required with the connection to Dept::getEmail()->send(...)

And also fix mishap events changing the ticket status

This patch removes several of the internal notes posted to a ticket for
various events and replaces them with events added to a threads event chain.
The emails are still sent out as they previously were, but internal notes
are only added to the thread if an agent actually specified comments.

If navigating back to the ticket queue (after closing a ticket, for
instance), return to the queue previously viewed.

Add ability to extend Form
Support the concept of form ID
Clear/hide field errors on blur

Unassign tickets on transfer when the target department has assignment
restriction and the assigned staff is not a member.

Disable claim (quick self-assignment) when above restriction is in effect.

This fixes a slight regression, where, if the locking mechanism were
disabled, then tickets could no longer be responded to.

Also, add warning popup when lock is about to expire and allow the user to
attempt to renew the lock. Also, connect the keyup callback for redactor to
the autoLock.handleEvent for greater update of the lock, and also deadband
the lock to every 10 seconds.

This patch includes a slight database migration, and adjusts the
functionality of a few core components.

  * Move collaborators from the ticket to the thread.
    This concept allows collaborators on any object which has a thread,
    including tasks.

  * Add flags to the thread entry
    This will allow flagging thread entries for different purposes.
    Initially this can be used to flag the original message of a thread in
    case a ticket / thread is created without an initial message.

  * Lock becomes more of a utility
    The lock is now disconnected from the ticket and is a separate utility.
    Separately, the ticket and task objects can have a reference to a lock
    object. Furthermore, when submitting some activities to tickets, the
    lock is verified to be owned by the respective agent, and the lock code
    must match a current lock code. The code is rotated on each acquire()
    call to guard against double submissions.

  * Collaborator is an ORM model
    The TicketUser class is broken up now so that the collaborator instance
    can exist apart from a ticket. Email message ids are now generated for
    collaborators without respect for a ticket so that collaborators can be
    properly supported on any thread.

Allow for permissions to be registered dynamically. This will
allow for the ability for models and plugins to register permissions.

Support duplicate names in different hierarchy
Save path on add/update
Show full department name on transfer

oops: Fix crash upgrading to c7c82835

oops: Fix crash rendering ticket view

oops: Fix crash posting response to ticket

oops: Fix refresh url after ticket reply post

orm: Locate annotations after the root model's fields

orm: Add PK field check for DISTINCT aggregate expressions

When using the DISTINCT option for aggregate expressions, ensure that when a
relationship is used in the aggregate, that a single field of the remote
model's primary key is used — rather than the foreign key, since it would
never have more than one unique value.

search: Re-implement basic ticket search

oops: Couple trivial changes

oops: Fix date formatting for PDF output

oops: Fix staff profile view and update

oops: Fix canned response listing

orm: Fix crash compiling WHERE IN (nested select)

nav: Move settings/email to email/settings

i18n: Make field visibility config translatable

oops: Fix crash adding field to custom form

forms: Fix `required` flag transfer to FormField

oops: Fix bad merge on new ticket by staff

forms: Show uneditable fields on new ticket by staff

oops: Fix bad merge on client ticket view