This is a regression introduced somewhere along the way in the new storage
API system for osTicket.

The warning was meant to be humorous but apparently the world has no sense
of humor.

Stop propagation on intercept

Credit: http://stackoverflow.com/a/7385673/2867073

Staff uploaded files, on new ticket, were getting attached to message instead of
response.

Turns out that the new authentication system incorrectly cancels the reset
tokens when it processes logins rather than after the user successfully
resets his/her password

If a client is already logged into the system and follows a second ticket
link, show the ticket instead of the list of tickets.

Stop propagation on intercept

Credit: http://stackoverflow.com/a/7385673/2867073

The warning was meant to be humorous but apparently the world has no sense
of humor.

Reported by @ntozier

Also allow an administrator to lift the force password change flag without
specifying a new password.

Separate authentication strike (excessive login attempts) count from timeout
enforcement.

User got emailed reply even when staff selected  -Do Not Email Reply-

Change z-index to overlay popup windows correctly

Remove any ticket locks staff has on logout.

Show ticket prview when a ticket number is clicked as opposed to ticket
view.
Add collaborator preview tab on ticket preview tool tip.

Processing fetching in ASC order of the last fetch time
Remove LIMIT of 10 emails per fetch
Flush the buffer and terminate the request cleanly on autocron

The change will allows staff to open a new ticket without going through the
"forced" user lookup popup. On cancel the staff is presented with a
simplified user info form with email and name being the only fields
required.

Fixup search for users with hits in an searchable authentication backend:

  * If there is a hit for the remote backend, include that in the search for
    local users by email address. If there is a hit locally for the same
    email address, then remove the remote hit from the search results.

Fixup typeahead results

  * Abort previous search requests when the user enters more text into the
    search fields. This makes the search box feel more consistent, and
    avoids the case where the user finishes typing and valid search hits
    never appear