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)

New Ticket UI:
- Clean up recipient section (adding user and collaborators)
- Give agents the option of who to send the new ticket alert to:
	- Alert to All
	- Alert to User
	- Alert to CC + User
	- Alert to BCC
	- Do not send an Alert
- Added option of adding new Users for cc/bcc section using the 'Add New' button

Post Reply UI:
- Instead of having to type to get the option of adding a new user in the cc/bcc boxes, put an Add New button
- Clean up Add New routine
	- Now when adding a new collaborator using the Add New button, the User's name will appear in the cc or bcc box as specified and the Agent can go ahead and write their reply rather than pulling up the manage collaborators popup and forcing the agent to have to save the collaborator changes before being able to type a reply
- Change the option "Reply to Collaborators" to "Reply to CC + User" to avoid confusion

- 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

- unset the sessions form data only in necessary places
- refer to a tasks number instead of id in internal notes
- use indexOf instead of includes in js for IE compatibility

Different email templates will now go out for BCC'd
collaborators so that the User will be able to know
they are blind copied on a ticket.

Template Names:
- New Activity Notice (BCC)
- New Ticket Notice (BCC)
- Response/Reply Template (BCC)

- say created from thread entry instead of created from thread
- make sure that links to thread entry do not open in new window
- make sure if default help topic is selected, message data carries over
  - make sure if issue details are not included for a help topic form, we
    make sure there is a message before trying to get attachments for one
- do not pass in an object to session array. use id and do lookup after instead

When a Task or Ticket is created from a Thread, this code
adds the functionality to create an Internal Note in the
new Ticket or Task as well as the original Ticker or
Task to show the activity that happened.

- In class.forms.php, $this->field->getClean() was null so $new was not populated and attachments were not being carried over, so we must get the fileIds directly from the form-data array
- We need to unset the form-data for attachment fields (on tasks and tickets) so that the array is empty each time we try to create a task or ticket from a thread
- We need to add files attached to threads where we are creating a task or ticket to the list of allowed files otherwise they will not carry over to new tasks/tickets (only files uploaded by this user in this session were allowed previously)

- 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

* kevin/issue/department-field-display:
  oops: Dept Field Display

- Fix to make sure tickets can be created from a User's message (not just Agents or Internal Notes)

- Save Filter Actions at the top of Filter::save
- Validate the Filter Actions before commiting the save

This is done to fix the issue where Depts/HT's said 'Unchanged' when initially saved. Now their configuration is set correctly before doing additional validations for active depts/hts

- change recipient name vars to 'Collaborator' in tmpls if ticket user isn't a recipient
- for templates going to Bcc'd Collaborators, account for all name format variables that could be used
- new function getNameFormats returns an array of all name formats in templates for staff.name.* or recipient.name.*
- other minor cc/bcc fixes

This fix uses 'filter' instead of 'findFirst' for finding Dept and Team referrals since the __in operator is not included in the evaluate function that was being called when using 'findFirst'

- function isReopenable needed to check for topic
- getHelpTopics for inline edit needed to include name of disabled Topic if selected
- getHelpTopics for dashboard needed to include disabled/archived Topics

Commit 3944b51d added ability to archive help topics and departments but
failed to port changes default data (yaml files) loaded on install.

This commits adds the correct bits to flags field for both help topics and
departments. It also removes retired 'isactive' field for help topics.

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 commit adds var_dump test along with a few enhancements on the test
script.

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.

This addresses an issue where you can exploit XSS in the help-topic AJAX
request. This adds a check for a refferal URL and if none it will return
a 403 Forbidden Response.

This addresses an issue where the CSRF Token is displayed in the URL
when you preform a search in the Users Tab. This removes the token from the
request which removes it from the URL.