- May 14, 2015
-
-
Jared Hancock authored
-
- May 13, 2015
-
-
Peter Rotich authored
Move collaboration implementation to thread level
-
Peter Rotich authored
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
Instead of selecting the first enabled, visible, non datepicker field, just use the new @autofucus HTML5 attribute to automatically select the autofocused field
-
Jared Hancock authored
-
Jared Hancock authored
Chosen has a problem being rendered in a dialog box with overflow:scroll, because the content of the dropdown widget is truncated with the scrollable content of the dialog. Select2 addresses the issue by placing the dropdown box in the <body> and absolutely positioning it into place.
-
Jared Hancock authored
This patch adds Content-Language and <link rel="alternate"> information to the client interface for better integration with search engines. It also adds @lang attribute to the <html> element and various input, textarea, and richtext boxes for better spell check integration and accuracy.
-
- May 05, 2015
-
-
Peter Rotich authored
-
Peter Rotich authored
-
Peter Rotich authored
-
Peter Rotich authored
This will allow for any threadable object to render the thread.
-
Peter Rotich authored
Add ability to extend Form Support the concept of form ID Clear/hide field errors on blur
-
Peter Rotich authored
Add a tab for tasks Add mass action for tasks
-
- Apr 30, 2015
-
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
Also add resend only option (for the case when "Edit and Resend" is not allowed).
-
Jared Hancock authored
-
Jared Hancock authored
Add in the ability for an agent to resend a response. Optionally editing the response before sending it, and setting the signature as is possible with the usual responses. When the response is resent, the edited version is marked as GUARDED, and subsequent edits will result in new links in the history chain. That is, when a response is edited and resent by an agent, that response will remain in the history chain.
-
Jared Hancock authored
Threads can be edited by marking the original as hidden and setting it's PID to the id of the new entry. The new entry has cloned data from the original and sets the `updated` timestamp to reflect the time of last edit. An edited flag is added to the new entry to reflect its origin. This patch suggests that agents can edit their own posts, department managers can edit posts while the ticket is in their department, and that help desk admins can edit anything. If a post is edited more than once, only the most recent edit is kept.
-
- Apr 15, 2015
-
-
Jared Hancock authored
This feature addresses a major issue with the initial implementation of the custom data system. The original system confused the usage of database-backed field (dynamic-fields) and their corresponding implementation. This created the need to crate awkward caching pieces to ensure that validation errors and data was maintained. Furthermore, the system confused the linking between form instances (dynamic-entry) and the form used to represent that entry. This patch addresses the confusion in two ways: Dynamic form entries do not link directly to the dynamic form. Instead, the ::getForm() method returns something from the forms API directly. Furthermore, the ::getFields() method does not return dynamic field instances (database backed / designed fields). Instead, the actual implementation of the fields from the forms API is retrieved. This allows the fields to *always* be cached, which helps preserve data and validation state. Secondly, the dynamic form uses the same system, so that requests to turn a dynamic form into a form (via ::getForm) will also result in the same behavior, again, where the fields are represented as forms API fields rather than the dynamic fields. So going forward, the dynamic fields are *only* used to create corresponding forms API field implementations. The are associated with the dynamic counterparts as sparingly as possible.
-
- Apr 09, 2015
-
-
Jared Hancock authored
-
- Mar 23, 2015
-
-
Jared Hancock authored
-
- Mar 18, 2015
-
-
Jared Hancock authored
-
- Mar 05, 2015
-
-
Jared Hancock authored
-
Jared Hancock authored
Also, convert the user tickets template file to use ORM
-
Jared Hancock authored
-
- Mar 03, 2015
-
-
Jared Hancock authored
-
- Feb 27, 2015
-
-
Peter Rotich authored
-
Jared Hancock authored
-
Jared Hancock authored
Allow the staff banner to be set to empty (which is the default). Also display the update errors back on the dialog for failed updated.
-
- Feb 26, 2015
-
-
Jared Hancock authored
-
- Feb 17, 2015
-
-
Jared Hancock authored
-
- Feb 10, 2015
-
-
Jared Hancock authored
-
Jared Hancock authored
This patch converts the central file and threading classes over to use the ORM.
-
- Jan 23, 2015
-
-
Jared Hancock authored
-
- Jan 13, 2015
-
-
Jared Hancock authored
* Add trashcan icon for newly-added actions * Categorize filter actions * Use imperative phrases for action descriptions * Drop check boxes from simple actions (like reject ticket) * Hide empty forms on new ticket pages * Do not store config for nondata fields for actions * Implement a multi-use feature for actions, which will allow using a action more than once (for instance, multiple email sends) * Filter actions are sortable * Send email has from address configurable * %{user} token is valid as a recipient
-
Jared Hancock authored
This patch rebases filters into a row-based layout and redesigns the filter apply method to be more extensible. It also redesigns the UI to be more dynamic and to allow for actions to be added without database modification and actions can also have complex configurations.
-