Use the topic associated with the email if any, and the topic defined as the
system default as the last resort. In either case, the form associated with
the help topic will be added to the ticket, but no data will be put into the
form fields.

Fixes #958

Add ability to remove users from organization

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

Also add several lint fixes for packaging

The user preview tool tip and edit dialog use the same user template.
Editing on preview mode resulted in partially hidden edit form. This fix
adds ability to popup a dialog modal on edit while on preview mode.

Conflicts:
	.gitignore

orbs: Allow inline edit, change, and creation

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

Improved import support

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

Several small tweaks to the client user experience

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

On the user profile page, the link to view the organization now triggers a
popup dialog which allows for changing and editing the organization directly
from the user profile page. An additional [Manage] button is added to the
dialog to allow redirect access to the organization page.

ee91d179 introduced a slightly different
tracking system for detecting sessions. Instead of completely disabling the
session system for AJAX and cron requests, it detects if the session is new
or not based on the session_id() and existing data in the session backend.

However, the patch did not correctly determine if a session was new.
Instead, it flagged all session as existing. This patch fixes the detection
of existing session data so that AJAX and cron requests can operate without
writing session data to the backend.

Instead, previously, a maxlength of zero effectively disabled the field,
because it prevented any user input into the field.

When following a link from an email, if you are already signed in to the
help desk as a client, you should just be redirected to the new ticket.