This will allow administrator to indicate if end users are allowed to reopen
tickets in a particular closed status.

This is necessary to avoid confusion vs. closed state.

Also fix crash if the [name] of a widget element started with a digit
character.

This allows fields to specify a visibility constraint that will be evaluated
in real time in the browser to automatically show and hide fields that
should be hidden based on values of other fields in the same form.

Validation is not performed on fields server-side if they are considered
invisible when submitted.

Redirect to tickets listing page when a ticket is resolved or closed via
status change.

Show different messages and placeholder on ticket(s) deletions

Make the error message clear

This will allow for more complex widgets to be added as plugins which
include css and javascript media files without manually adding header or
footer lines.

Cleanup status change form
Add resolve to ticket ticket view
Use the new status table when checking for overdue

Unify use of modal dialog
Make popup dialog graggable

Statuses with tickets cannot be deleted
Fix orm to class gracefully when joins are not inspected
Add create date to new statuses

Reserve 'archived' state for automation

Move ticket status change to unified backend.

Add other locations as well a failsafe for the htmlentities() call

Ticket numbers are now configurable as a system-default and by help topic.
Previously, an administrator could select between six-digit random and
sequential numbers. Now, the sequence is selectable so multiple sequences
as needed, and a format can be specified to define how the ticket numbers
look. Formats can also be defined for each help topic.

References:
(Requires Crowdin account)
http://i18n.osticket.com/translate/osticket-official/148/enus-de#3852

Names parsed from incoming emails are stored in the database as is. This
pull request addresses potential XSS vulnerability due to improper display
of unsanitized names. Going forward names will be scrubbed on create.

If a list item properties form was unable to be saved (likely due to
validation errors) properties for other list items would not be loaded
correctly (via AJAX) afterwards.