This removes a significant number of queries used to render the drop-down
menu for the queues.

Each queue displayed on the page previously required a database query to
determine its children. This patch changes the strategy to fetch all the
queues and organize them as a tree. The tree can then be walked as the menu
is rendered and does not require any further queries.

On my test system, it reduces the number of queries for the ticket listing
page from 56 to 46.

This might happen if the close date was added to a queue and filtered
through a date/time filter.

Also fix warning emit when editing queue configuration

Also fix a few crashes if there is a naming mismatch on the field named in
search criteria and the current name of the field. And fix a regression
where the queue criteria would not be properly updated when saved.

If a queue inherits columns from a parent, the conditions would also be
inherited. This fix changes the association by linking the inherited
column to the child queue at run-time. This allows the queue column to
fetch the queue conditions from the child queue which inherited the
columns.

Check 'inherit columns' checkbox when cloning a queue

Fix doubled saved search listing

- Clean up/correct notifyCollaborators function
- Make sure function calls are passing in all needed variables
- getContact function added to EmailRecipient class to properly set up email notifications
- Corrections on encoding recipients for thread entries

This feature adds a new Role permission called Release. This permission
(if Enabled) allows an Agent to release ticket assignment. This permission
is configurable for each and every Role in the helpdesk. This also keeps
current functionality where Department Managers do not need the Role
Permission in order to release tickets. In addition to the permission,
this feature adds a new Release modal giving the option to choose who to
release assignment from (Agent/Team/Both). This also adds a comment box to
the release modal to optionally enter a reason for releasing assignment.
Lastly, this adds a Release Thread Event so an event is logged showing who
released who’s assignment.

This addresses an issue where the Queue Export does not remember your
column sorting. This was due to the `getExportableFields()` function
called in the Export Template that gets a predefined list of fields plus
some `cdata` fields with a predefined sort order (not your saved sort
order). This updates the export template to merge the `$fields` array that
contains the exportable fields in the saved sorting order and the
`getExportableFields()` result (array) that contains the same fields plus
`cdata` fields. This will return the fields in the saved sorting order
whilst still displaying possible `cdata` fields.

This means Agents can no longer choose to add a BCC User while creating or responding to a Ticket.

This also means that if a User emails in a Ticket where someone is BCC'd, the Ticket will be created without the BCC'd User(s).

If an email is sent where the Department email is BCC'd, a Ticket is created for that Department and other Users in the email are added as Collaborators.

This also changes the response options for Agents. They now have the options to:
- Reply All (User + Collaborators)
- Reply to User (only the User)
- Do not Email Reply

(Previously the options were Reply All, Reply to User, Reply to CC + User, Reply to BCC, Do not Email Reply)

- Change To dropdown to have different reply types
	- Reply to All
	- Reply to User
	- Reply to Collaborators
	- Reply to BCC
- Add a help tip for the new reply types
- Set the reply type selected based on the last user respondent
	- Reply to Collaborator by default or if the last message is from the ticket user or a CC collaborator
	- Reply to BCC if the last message is from a BCC user
- Put User, CC, and Bcc fields below and indented as appropriate (User field is readonly)
- Add a new flag to Agent responses to show which reply type they selected. Put the flag on Agent thread entries

Don't display the Close Task option if the current user can't close it...

This addresses an issue where the User’s account status is always 'Active'
in the Organization list no matter what their actual status is. This adds the
account status to the user query which adds the correct status to the Users’
account.

- On ticket edit, only display inactive help topic warning if the ticket has a help topic
- Inline edit file save fix
- Remove future search/filter criteria for datetime fields that can't be in the future
- Fix calculations for 'next 7 days' and 'next 30 days'. They were selecting dates between now and n days AGO instead of between now and n days in the future

This addresses an issue where the Ticket Preview is broken no matter if it
has a custom field attached or not. This corrects a typo for `$thisstaff`
so the system can get the Agent’s Role to complete the rest of the preview
options.

This addresses an issue where unchecking the box for 'Inherit columns from
the parent queue' does not hide the columns from the parent queue. Instead
it pushes them below the new, editable columns. This adds jQuery to toggle
the visibility of the parent columns.

* Ticket preview crash
* Task view crash

This commits adds ability for agents to configure public queues.

* Customize Columns
* Set default sort & quick filter
* Add supplemental filters (criteria)

To support above features this commit also addresses confusing Advanced
Search UI to make it intuitive when dealing with a Saved Queue vs. Saved
Search vs. Adhoc Search

This addresses an issue where the User’s account status is always 'Active'
in the Organization list no matter what their actual status is. This adds the
account status to the user query which adds the correct status to the Users’
account.

Only ignore visibility constraints on private "searches" when staff is allowed to search the backend.
Access control is strictly imposed on ALL queues including inherited private sub-queues.

Commit c4579277 introduced an extra administrative security feature to
restrict files access to signed in users only, even  if a user has a valid
& signed download URL. The feature, however, did not take into account
public images & files associated with FAQs and pages such as
landing/thank-you pages.

This commit addresses the shortcoming by adding a reference ID (attachment ID)
to the download/access URL, that can be used to deduce the model/object type
that the file request is associated with. The technique will allow us in the
future to enforce ACL at the file level depending on privacy settings and
the security clearance of the user (agent).

Account for the possibility of agents being deleted

Unify ticket visibility as a routine to make sure it's applied uniformly.

This adds a Ticket Thread Action for creating a Task. This action will
popup the New Task modal and will pre-fill the body of the New Task with
the body of the Thread Entry from which the action was made from.

Example:
Thread Entry - “I will need to check on the status of your account.”
Click Create Task from that Thread’s Actions
System will show New Task popup with the body as “I will need to check on
the status of your account.”

* Make saving advanced ticket search intuitive
* Make save separate operation from search (primary)
* Show inherited criteria on parent queue change

Add ability to select fields / columns to export for queues, including adhoc
searches.

This addresses an issue where the Delete Task Action Button had the wrong
classes which gave it the wrong styling. This corrects the class to make
the Delete button look like the other buttons and still have the red
background on hover.

* 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.

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

Don't display the Close Task option if the current user can't close it...

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.

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.