* Export all exportable fields by default - for all queues + adhoc searches
* Export Due Date as well as SLA Due Date

Add ability to add sticky export fields for queues.

* Due date vs. SLA due date
* Misc. datetime fixes

Add ability to edit individual fields without the need to mass-edit all
fields.

Conflicts:
	include/class.thread.php
	include/class.ticket.php

Add support auto email-based auto-referral. This will happen if an email is
sent to multiple departments. For example an email with TO: support &  CC:
billing will result in the ticket getting routed to "support" department and
"billing" getting a referral of the same ticket. This allows both departments
to have visibility of the ticket - which is not possible at the moment.

Move referral checking to thread class

Move referral checking to thread class

Refer ticket to current assignee on reassignment
Refer ticket to current department on transfer

Add the initial concept of thread (tickets & tasks) referral.

* Agent & Team
Referring a ticket to an agent or team - is just like assignment without
actually assigning. If referred agent doesn't have access to the ticket's
department then they'll only have view access.

* Department
This is like assigning a ticket to the entire department. Meaning agents who
have access to the referred to department will now see the ticket - what
they can do with the ticket will depend on the assigned role in that
particular department.

It's important to note the ticket will technically be still the
responsibility of the primary department. Transferring the ticket is the
sure way to relinquishing the responsibility.

* Auto Department Referral via email
This will happen if an email is sent to multiple departments. For example an
email with TO: support &  CC: billing will result in the ticket getting
routed to "support" department and "billing" getting a referral of the same
ticket. This allows both departments to have visibility of the ticket -
which is not possible at the moment.

This addresses issue 3815 where searching by User's phone number doesn't
work in v1.10. This adds phone number search capabilities for the User
Directory and User Search popup in v1.10.

Limit the departments based on Agent's access

Refer ticket to current assignee on reassignment
Refer ticket to current department on transfer

Add the initial concept of thread (tickets & tasks) referral.

* Agent & Team
Referring a ticket to an agent or team - is just like assignment without
actually assigning. If referred agent doesn't have access to the ticket's
department then they'll only have view access.

* Department
This is like assigning a ticket to the entire department. Meaning agents who
have access to the referred to department will now see the ticket - what
they can do with the ticket will depend on the assigned role in that
particular department.

It's important to note the ticket will technically be still the
responsibility of the primary department. Transferring the ticket is the
sure way to relinquishing the responsibility.

* Auto Department Referral via email
This will happen if an email is sent to multiple departments. For example an
email with TO: support &  CC: billing will result in the ticket getting
routed to "support" department and "billing" getting a referral of the same
ticket. This allows both departments to have visibility of the ticket -
which is not possible at the moment.

This addresses issue 3815 where searching by User's phone number doesn't
work in v1.10. This adds phone number search capabilities for the User
Directory and User Search popup in v1.10.

Limit the departments based on Agent's access

Currently only windows of a specific number of days is supported. Things
like `last month` are much more complex.

The ticket status search field was supposed to mimic a text field rather
than a drop-down field like the status selection.

Also, since select "TicketStatus / State" from the drop-down list doesn't
work, remove items from the drop-down in the advanced search dialog and
queue management page which would duplicate fields already available or
selected in the list of fields already displayed.

Fixes the SQL generated for scans by staff_id and team_id on the ticket
table. The fields are not nullable. Instead, the value `0` represents not
having a value.

This allows a queue to define conditions which apply to the entire row, so
that all the columns in a row can react to a particular condition. For
instance, rows in the ticket queue for tickets due in the near future or
assigned to a particular team could be formatted a certain way.