This addresses issue 4473 where users creating a ticket with the Help Topic
preselected shows a validation error for the Issue Summary field. This is
due to the new `getFormName()` function that creates new field form names
based on the user’s/agent’s session. When the Help Topic is preselected,
`_form` is not set for each field so the hashed name of the fields before
ticket submit is different than after ticket submit.

This commit fixes the way we validate filter actions before saving a filter. Now, the code will accurately validate the action without needing a filter_id first while making sure all validations stay withing the validate_actions function.

This addresses an issue where images in email signatures containing a
`data-cid` attribute will either crash the ticket page or not show the image
in the signature.

This addresses issue 4470 where Users creating tickets via Client Portal and
failing to fill out a required field makes disabled fields by Help Topic
appear on the page. When the disabled fields appear they allow Users to
populate and save data that they were not meant to submit.

This addresses an issue where people who do not have a phone field on the
contact information form go to search for a User in the User Directory and
the system crashes. This is due to the search query that always contains the
phone field variable. This only adds the phone variable to the search query
if the field actually exists.

This will be useful when converting content on the fly on write or read -
allowing for support for output filter for file storage backend.

This addresses an issue where `SetAutoFont()` was making the Thai PDFs
break. This adds the `AUTOFONT_RTL` flag to only autodetect RTL languages
and nothing else.

This addresses an issue where creating an advanced search with selection
field "does not have a value" throws a fatal error. This was due to an
improperly named search method "notset".

This commit fixes an issue where the ORM was trying to get invalid Staff fields (which we actually store in the config table), therefore throwing an error.

This adds functionality to clean expired password reset tokens on cron runs.

This addresses an issue where FileUploadFields on the ticket header is not
displaying all attachments in the field.

This adds a Signal to clean Agent and User sessions upon setting/resetting
their password. If an Agent/User resets their own password and has multiple
sessions open it will log them out of every session except the one they’re
on.

This commit addresses the root cause of an issue commit 96892beb (now
        reverted) attempted to solve - by providing consistency between
getFiles and getAttachments

This addresses an issue where row conditions are working in the preview but
not in the actual ticket queue. This updates the `getQueue()` function to
lookup the CustomQueue by `queue_id` if there is no CustomQueue object found
in the QueueColumn.

This addresses issue 4449 where using an Arabic language pack and trying to
print a ticket returns a PDF with either squares for text or no text at all.

This addresses an issue where searching for a Task by title returns all
Tasks in the search. This is due to the visibility filtering methods used to
filter tickets by staff's visibility.

This commit removes the logic that was used for time within 2 days which would give a result of either today or tomorrow when something could actually be in 2 days instead.

It also rounds relative time that is within 29 days so that the result will be more accurate.
Ex: 1.99 will round to 2 instead of showing 1

This addresses an issue where Column Conditions are not overwriting the Row
Conditions. This changes the order of `array_merge()` to make Column
Conditions overwrite the Row Conditions.

This alphabetizes all Role and Staff Permissions.

This addresses an issue reported on the forums where the ticket filter Rule
option of “Does Not Match Regex” isn’t working properly; instead it works in
reverse.

This addresses an issue where it appeared as though tasks could not be assigned to teams if an agent in the team was not a part of the task's department. The assigment was actually taking place, however, it was not showing up in the Assignee column. Now the form will correctly display the column

This addresses an issue where uploading a file you’ve uploaded before but
renamed is not saving the new name in the Attachment table.

This addresses an issue where FileUploadFields are displaying the old names
of existing files with new names.

If an Agent has the Miscellaneous setting checked to see all Tickets in search results, they should be able to see the list of Tickets regardless of their access or if the search is saved or not. They should NOT, however, be able to view those Tickets.

This commit adds 'TicketStatus / Status Name' to the main search criteria list for advanced searching.

Retain old search criteria when isolate fails. This provide for ability to
fix issues with isolation post-upgrade.

- Enable/Disable Collaborators based on which Collaborators are in the 'Select Active Collaborators' box

This addresses an issue where the client portal shows Featured FAQs on the
sidebar even thought the Knowledgebase is Disabled.

This commit adds an additional check for Team referrals in the isReferred method so that it is handled in the same way Staff and Departments are handled.

This commit fixes an issue where referrals were being considered successfully saved even if that referral already existed, resulting in multiple thread events for the same referral.

Instead, if we find that the thread is already referred to the referee, refer should return false so that an error message is displayed stating that we were unable to refer the ticket.

This addresses an issue introduced with `9ab2317e` where the icon for the
event still shows even though we continued and didn’t return the event
description.

This addresses an issue introduced with `510046c5` where tickets with no
Help Topic can not be reopened. This is due to a check on `isReopenable()`
where it returns `null` instead of `true` if there is no help topic;
therefore returning false and not allowing the ticket to be reopened.

This reverts commit 14bcd42d.

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

This addresses issue 4155 where editing a ticket using a different session
causes custom file uploads to drop from the ticket.

This commit addresses an issue where the validation error for trying to save a Ticket without a Help Topic was not being shown as a result of the error message that was added to ensure that the Help Topic selected is Active.

This commit adds an Admin setting that requires a Ticket to have a Help Topic before it can be closed. It can be set by going to:

Admin Panel | Settings | Tickets | Require Help Topic to Close

If enabled, Tickets will have a warning banner across the bottom of the page, a warning banner when trying to change the Ticket status to Closed, and a warning flag beside the field when editing the Ticket.

By default, this setting is NOT enabled.