alerts: Consider "alert assigned on new message"

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

i18n: Automate dns signature publishing for language packs

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

csv: Add UTF-8 BOM to export file

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

faq: Show proper internal/public category in drop-down

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

dashboard: Fix initial page load and stats pagination

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

kb: Add setting to enable only for authenticated clients

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

search: Fix search on create date

Clear overdue on close

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

oops: Fix dropped custom data from API requests

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

filter: Trim match values when saving rules

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

Fixed typo

cdata: Drop ticket cdata on delete

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

files: Clear attachment box after posting a response

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

thread: Log remote IP for staff replies and notes

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

Because CSV has no way of indicating a content character set, writing the
file with a Unicode byte-order mark is useful to declare the content in
UTF-8 encoding.

When sending alerts to agents, consider the setting of the new message alert
configuration.

This addresses the issue where the advanced search dialog was submitted
before the date picker inputs were fixed up. This problem arises out of a
difference between the agent's date formatting preference and the server
being able to process that date format. The date pickers are reformated to
yyyy-mm-dd before submission; however, for advanced search, the submission
happened before the inputs were fixed up.

This patch addresses the issue by manually fixing up the date in the
submission routine for the advanced search dialog.

This will help when saving rules with trailing spaces for instance, which
may make things not match when visually the administrator would otherwise
expect the filter to match.

Fixes #1834

For a yet unknown reason, the association between the field implementations
and the DynamicFormEntry object is not maintained from calls to
DynamicFormEntry::getFields().

This patch addresses the issue by always associating the "form" when
returning from ::getFields()

wording: must be agents, because its agents table

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

Fixed typos in scp/helptopics.php

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

forms: Fix a couple places where validation errors are not propagated

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

Preserve the fields indexed keys
Only sort the fields once, after adding missing fields

Reset field content when building a new form

i18n: Missing translation "Add Organization"

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

See: http://osticket.com/forum/discussion/85083/osticket-sends-no-html-mails#latest

Looked at crowdin and the term "Add Organization" is already used in the following context:
#: include/staff/templates/org-lookup.tmpl.php:82

So my suggestion is to use it also for this context here, which would not require a new translation ;)

Michael