This is similar to the section break but doesn't have the <hr> element
before it and allows for HTML input (including images)

Dependent fields

Reviewed-By: Jared Hancock <jared@osticket.com>

Ticket statuses revisited

Reviewed-By: Jared Hancock <jared@osticket.com>

Hide multi selection option for typeahead selections

Consider current status settings to determine if a ticket is reopen-able
Show a warning on staff's ticket view if the ticket is not reopen-able

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

Hiding a field triggers visibility check on dependent fields
Use jQuery specific value getters

This will be useful for maintaining arbitrary list of items. ListObject
should be used in the place of ArrayObject

file: Propery support IE10 for file uploads

Reviewed-By: Peter Rotich <peter@osticket.com>

Use data view for ticket table client side

Reviewed-By: Peter Rotich <peter@osticket.com>

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 administrators to define a regular expression to filter content
entered into short answer fields by agents and endusers. With the new
visibility feature, the regular expression input is only shown if the
regular expression validator is selected.

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.

bug: Fix status display on client interface

Shameless-Self-Merge: <peter@osticket.com>

bug: Allow Resolved tickets to be reopened

Reviewed-By: Jared Hancock <jared@osticket.com>

oops: Fix crash in enduser web portal on reply

Reviewed-By: Peter Rotich <peter@osticket.com>

email: Improve user identification from headers

Reviewed-By: Peter Rotich <peter@osticket.com>

This is the correct logic - we'll address issue #1259 separately

Reviewed-By: Peter Rotich <peter@osticket.com>

Previously, the code would scan the email headers until it found a positive
match from any of the email headers scanned. Additionally, it would attempt
to find the user from the tagged email references header. However, this
algorithm assumed that the references header was constant and predictable in
its ordering. Recent tests with Gmail prove otherwise in some tests.

This patch changes the system so that only the tagged reference header is
included in the References header, and it will scan all items in a header
(namely the References header) until both the thread and a user are
identified. If a user can be identified, the thread and user are returned.
Otherwise, the first thread hit is returned.

Ticket status change

Reviewed-By: Jared Hancock <jared@osticket.com>

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

Show different messages and placeholder on ticket(s) deletions