profile: Reply Redirect

Issue: Can’t use “0” in Short Answer Field

This commit fixes an issue where a Short Answer Field would show as Empty if the value saved in it was '0'

Issue: Edit Export Column Heading

issue: Task Response With Collaborators

issue: Scrollable Quickfilters

Task Collaborators

Issue: Duplicate Search Results

This pull adds a Profile Setting for Agents to choose where to redirect
after replying to ticket. The two options are Queue (redirect to queue to
work on other tickets) or Ticket (redirect back to same ticket to continue
working) with the latter being the default. The setting is configurable for
each Agent in the helpdesk.

This addresses an issue where having more than 30+ choices for a Quickfilter
makes the dropdown run off the page causing some choices to be hidden. This
makes it to where if you have more than 20+ choices we will make the
dropdown a fixed height and make it scrollable.

This addresses a fatal error when adding a new response to a Task with
Collaborators. When we implemented the MailingList for Users/Collaborators
we forgot about the little Task Collaborators (poor little guys). This adds
a new function called `getRecipients()` to `class Thread` that utilizes
MailingList instead of UserList. This also adds two new functions to `class
Util` that retrieves the User’s `user_id`.

Peter approved merge

- Make sure we only set Filter Flags if they need to be changed (don't update them every time we save)
- Make sure we sure we use the email_id if we have actually set it. Otherwise, we lose what should be set for the Target Channel

This commit ensures that we do not return duplicate results when searching for Tickets with an Advanced Search that contains keywords.

Clarify User Import Instructions

This commit updates the instructions for User imports letting the Agent know they should type 'Name, Email' on the first line and then put each new User Name/Email on the following lines to import Users.

This commit addresses an issue where we did not save headings for export fields.
We just need to leave the heading in the array rather than filtering it out so that we can save its new heading.

This commit changes the wording for Collaborators on Tasks to match the wording for Collaborators on Tickets.

oops: markAs() Typo

issue: markAs() elseif

This addresses an issue where Department Managers would not see the option
for Marking tickets as (un)answered due to an elseif (should be an if
instead).

This addresses a typo in the `markAs()` function in `ajax.tickets.php`. DOH!
Should’ve ran the lint tests

feature: Public Mark As Answered/Unanswered

This feature extends the ability to mark tickets as Answered/Unanswered to
any Agent with the Role Permission to Post Reply in the Department. This
also adds the ability to add an (optional) Internal Note when marking as
(un)answered.

feature: Complete Thread Variable

Support using %{ticket.thread} to export the entire ticket thread
correspondence between agents and end users (owner + collaborators).

Field: Help Topic Forms

Don't show fields disabled by help topic
Pass create mode for pre-selected help topic forms

Forms: Field Permissions

issue: FAQ/Page Attachments

This commit addresses inconsistencies on how field edit rights and
visibility are are handled.

This addresses an issue where inserting images on a Page or FAQ and having
the setting enabled for "Login required to view attachments." does not
display the images at all when the Page/FAQ renders in view. This is due to
the Page/FAQ update functions that were not updated to fit the new
`id=>name` format for `keepOnlyFileIds()` introduced with `f179cf15`.

issue: Email Default Dept

issue: create_date Variable

This addresses an issue where the create_date variable is showing as Unix
timestamp instead of formatted date. This was due to a typo introduced in
commit `8623ed60` where the `$format` argument was forgotten for
`Format::datetime()` in the `FormattedLocalDate::getVar()` method.

This addresses an issue where configuring a System Email to have a
Department and then editing/saving changes on the configured Department will
change the System Email's Department back to the the default Department.
This was due to a un-needed Department Status check introduced with commit
`1d361b51`. This also updates all instances of Dept Status comparison to be
case insensitive and non-translated.

Deleting the Default Queue

queue: Top-Level Ticket Counts

FileUploadField Validation

This commit fixes an issue where Agents were able to delete their default queue which then prevented them from going to any queue upon logging in. Now, they will see an error message if they try to do so.