They are only available for tickets arriving via the email channel. All
other channel (including email) use the new ticket form to record the
subject and body, which are mapped to the 'Issue Summary' and 'Issue
Details' fields respectively

Structure the drop-down list for the `what` column to be future-minded
concerning custom user data matching.

Also removes the fetching of priorities separately and addresses sorting of
priorities by the ID field rather than the urgency field.

This reverts commit bc773adb.

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

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.

Include collaborator tickets on search by user.

Previously you had to click "Save Changes" for the count to be reflected on
ticket view page.

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

  * 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

The concept of extid is being retired to pave-way for customizatable ticket
numbers.

authentication backend.

Arrange templates in a group by their respective use in the system:

  * System Management Templates
  * Staff Ticket Templates (Alerts and Notices)
  * End-User Ticket Templates (Autoresponder)

This provides an interface to sort the templates and make them easier to
find and provides a nice place for new templates to be added without making
it increasingly more difficult to locate templates in the list.

This patch also fixes the missing templates in the drop-down list when
editing an implemented template.

Extra forms associated with the help topic are now shown above the ticket
details form on both the staff and client interfaces.

Fix dropping of materialized view when variable name is changed

Ensure view exists before merging updates

Prevent possible sql injection error in field name used in the materialized
view.

Prevent possible xss error in the display of the field label and variable
name in the admin panel.

Use a union query to avoid using DISTINCT and lots and lots of joins in the
from clause.

Initial tests seem to indicate about a 80% faster (~500ms down from ~800ms)
on querying about 9k tickets).

And make plugin internal handling more consistent

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

This patch introduces an automatic materialized view to speed database
performance when querying and displaying the ticket views. This can
eventually be extended to the search and advanced search features to speed
them as well.

The data from the dynamic form entries related to ticket details is copied
to a %ticket__cdata table. The %ticket__cdata table is then joined directly
to the other tables in the query for the ticket view. MySQL is magically
and dramatically faster using this method.

The downside is that the disk usage for the custom data is doubled, and the
time needed to update the dynamic data is at least doubled as the form
entries and the materialized view must both be updated.

This method should also extend well to other database platforms in the
future. It will be likely that most other database query optimizers will
have difficulty joining, scanning, and sorting the table models we have for
custom data fields.

And define getInitials() function for %{ticket.name.initials}