Internal Email Forwarding

Issue: Agent Export Department Status

Issue: Translating Archive Selections

This commit changes the Agent export to display (disabled) beside the name of Departments on the export if they are Archived or Disabled. This will help Agents determine if an Agent is not assigned to any active Departments.

This commit avoids camel casing the select values for Archiving Help Topic and Department options. It also fixes an issue where the selected value was being translated and it should not have been.

Give agents department's ticket / task create, by default, unless explicitly
denied by an assigned role.

Make subjects bold (by default) when ticket is unanswered

Add ticket reopen count as a column annotation

Issue: Dumping Tickets From User View

Agent Ticket on Behalf of User Fix:

Issue: New Task Department Sorting

This commit fixes an issue where Departments were not in alphabetical order when opening a new Task. This will also ensure that Departments will be alphabetically sorted anywhere that contains a DepartmentField.

This commit fixes an issue with how we export tickets from a specific User. Since changes were made to how Ticket exports are done, we needed to modify the call to export the Tickets from users.php as well since we were unintentionally sending the file name in where the csv headers should've been (variable added in dumpTickets method).

This commit fixes an Issue that resulted from allowing Agents to add Collaborators when opening a Ticket on behalf of a User and being able to decide who will receive an email alert. If an Agent were to add an initial response to the Ticket, two email alerts would be sent out (New Ticket Notice and Response/Reply Template). Now, only the New Ticket Notice is sent out unless the Agent chooses not to send any alert.

Additionally, if the Autoresponder is set to NOT alert a User when an Agent creates a ticket on their behalf and the Agent includes an initial Agent response, the Response/Reply Template is sent out.

Addresses issue with agent/assignee sorting

Conflicts:
	include/staff/ticket-view.inc.php

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

Conflicts:
	WHATSNEW.md

Conflicts:
	WHATSNEW.md
	include/class.format.php

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.

This addresses an issue where the Help Text for Section Break fields does
not display custom Redactor styling correctly. Instead of displaying the
properly formatted Redactor content with it's styling it displays the
entire html for the Redactor content. This was due to the format method
used for the Section Break Field's Help Text. This updates the method from
`Format::htmlchars()` to `Format::display()` which displays the properly
formatted content. The content is also sanitized by `Format::sanitize()`
before saving to the database to avoid any chance of XSS.

This fixes an error where the ModelInstanceManager maintained a reference to
the QuerySet instance, and the QuerySet instance managed a reference to the
ModelInstanceManager instance (if it's the iterator for the query). Because
of the circular reference, if the iterator is not exhausted, then the
resource is not closed and the query remains open. This wastes memory and
prevents some other queries from running after such a situation happens.

This addresses the issue by removing the circular reference between the
QuerySet and the ModelInstanceManager.