Add ability to disable canned responses
Fix team drop down selection
Remove priority escalation setting in SLA page (implementation is on todo
        list)

Add department setting to limit ticket assignment within department to
department members only. This is necessary for departments with strict
policy on who can access tickets.

The setting doesn't limit team assignment or auto-assignment via help topics
and ticket filters.

Client accounts now that the user is verified either via staff or the
client's email mailbox, there's a much lower risk to showing a verified user
other tickets and virtually no reason that an administrator should have to
turn the feature on.

Add client registration methods and login required checkbox

  * Administrator can disable the new activity alert
  * Administrator can disable automatic collaborators from email headers

Administrators can disable client edits of ticket information. Hopefully,
this will eventually be replaced by role-based ACLs placed on individual
forms and fields.

  * Include a `bk` column to store the storage backend
  * Include a `signature` column which represents a repeatable hash of the
    file contents
  * Rename `hash` to `key` since it isn't a real hash

And install initial data in target language. Also configure help tip
popovers to be in the configured, default system language.

If a ticket is currently unassigned and your respond to it, it's yours. If a
ticket is closed and later reopened due to a new message, the last
respondent will always be assigned if available at the time.

This includes the initial concept of pluggable authentication along with the
initial concept for a plugin management system.

And extend the information to email templates

Move the cacheable code to the Http class and allow the client configuration
to be cached in the browser

Process inline attachments in thread entry and support inline images in
piped emails

Support inline images across the system, with draft support

Migrate to a single attachment table
    That way we don't need a new table for everything we need to attach an
    inline image to (like a signature, for instance)

Add richtext support for internal notes

Implement images on site pages

* Image paste in Redactor
* Make non-local images optional
* Placeholder for non-local images
* Fix local image download hover
* Don't re-attach inline images

If it only contains whitespace, it is also invalid

Which will help against clobbering session cookies against other PHP
applications shared on a parent domain of the domain hosting osTicket or in
a parent folder or virtual folder.

Uses a seven step procedure:
  1. (user) Fails to login twice or more
  2. Clicks the 'Forgot my password' link on the login form
  3. Submits the username or email address and triggers a password-reset
     email
  4. Clicks the link in the email and is directed back to the reset page
  5. Enters the username or email again and is logged in
  6. Password change is forced, but current password is not required
  7. Password is updated, user can continue the session without
     authenticating again

Use %config table by default for config classes

Add lastModified() method to retrieve the time of last modification for a
configuration key

Add $defaults to the specified on a subclass. The defaults remove the
necessity to specify a default value for each getter method, and, the
defaults are integrated into the array retrieved from getInfo()

Administrators are allowed to upload one or more logos and then select from
the uploaded logos to set one for the client site. Logos can also be deleted
on settings->pages submission

SLAs can be marked transient. When a ticket is assigned to a transient SLA
and it is transferred to a department or help topic having a default SLA,
the SLA will change to the SLA of the new department or help topic. This
process can continue as long as the ticket has a transient SLA assigned.
Once a non-transient SLA is assigned to the ticket, the SLA will no longer
change automatically. Thereafter, the SLA can only be manually changed.

This will allow setting something in the session and having that value
override the value from the database. If ->persist() is called for a given
key, a following ->get() will result in the session persisted value being
returned. ->set() will still save the value in the database.

This is mostly useful for last-mile scenarios (and future plugins) that need
to affect the configuration of the system without altering the data in the
configuration table.