- May 22, 2015
-
-
Jared Hancock authored
-
- May 21, 2015
-
-
Jared Hancock authored
This fixes a bug where the search queue would be empty when accessing it via the navigation link
-
- May 20, 2015
-
-
Jared Hancock authored
-
- May 14, 2015
-
-
Jared Hancock authored
-
- May 13, 2015
-
-
Jared Hancock authored
Also, fix the links to the ticket queue search (again)
-
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
Also, fix the links to the ticket queue search (again)
-
Jared Hancock authored
If navigating back to the ticket queue (after closing a ticket, for instance), return to the queue previously viewed.
-
- May 11, 2015
-
-
Jared Hancock authored
-
- May 05, 2015
-
-
Peter Rotich authored
-
- Apr 30, 2015
-
-
Jared Hancock authored
-
Jared Hancock authored
-
- Apr 16, 2015
-
-
Jared Hancock authored
Fixes #1854
-
- Apr 14, 2015
-
-
Jared Hancock authored
-
- Mar 23, 2015
-
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
- Mar 20, 2015
-
-
Peter Rotich authored
Support filtering search results by uid.
-
- Mar 17, 2015
-
-
Jared Hancock authored
-
- Mar 05, 2015
-
-
Jared Hancock authored
-
Jared Hancock authored
Also, convert the user tickets template file to use ORM
-
- Feb 26, 2015
-
-
Jared Hancock authored
-
- Feb 12, 2015
-
-
Jared Hancock authored
This patch includes a slight database migration, and adjusts the functionality of a few core components. * Move collaborators from the ticket to the thread. This concept allows collaborators on any object which has a thread, including tasks. * Add flags to the thread entry This will allow flagging thread entries for different purposes. Initially this can be used to flag the original message of a thread in case a ticket / thread is created without an initial message. * Lock becomes more of a utility The lock is now disconnected from the ticket and is a separate utility. Separately, the ticket and task objects can have a reference to a lock object. Furthermore, when submitting some activities to tickets, the lock is verified to be owned by the respective agent, and the lock code must match a current lock code. The code is rotated on each acquire() call to guard against double submissions. * Collaborator is an ORM model The TicketUser class is broken up now so that the collaborator instance can exist apart from a ticket. Email message ids are now generated for collaborators without respect for a ticket so that collaborators can be properly supported on any thread.
-
- Jan 07, 2015
-
-
Jared Hancock authored
-
- Jan 02, 2015
-
-
Jared Hancock authored
* Fix translation of pages * Localize client thank-you page on new ticket * Fix adding new category * Fix crash on staff login when upgrading from < 1.9 * Don't show self locks on ticket queue pages
-
- Dec 30, 2014
-
-
Peter Rotich authored
Use http::build_query instead of inline urlencode
-
- Dec 20, 2014
-
-
Peter Rotich authored
Allow for permissions to be registered dynamically. This will allow for the ability for models and plugins to register permissions.
-
- Dec 11, 2014
-
-
Jared Hancock authored
-
Peter Rotich authored
-
Peter Rotich authored
-
Peter Rotich authored
Generalize how we show object/data preview. The url to get the preview is now based on data-preview attribute on the element in question.
-
Peter Rotich authored
Use generic attachment table for all attachments system-wide. Drop thread entry attachment table
-
Jared Hancock authored
-
- Dec 10, 2014
-
-
Jared Hancock authored
-
Jared Hancock authored
oops: Fix crash upgrading to c7c82835 oops: Fix crash rendering ticket view oops: Fix crash posting response to ticket oops: Fix refresh url after ticket reply post orm: Locate annotations after the root model's fields orm: Add PK field check for DISTINCT aggregate expressions When using the DISTINCT option for aggregate expressions, ensure that when a relationship is used in the aggregate, that a single field of the remote model's primary key is used — rather than the foreign key, since it would never have more than one unique value. search: Re-implement basic ticket search oops: Couple trivial changes oops: Fix date formatting for PDF output oops: Fix staff profile view and update oops: Fix canned response listing orm: Fix crash compiling WHERE IN (nested select) nav: Move settings/email to email/settings i18n: Make field visibility config translatable oops: Fix crash adding field to custom form forms: Fix `required` flag transfer to FormField oops: Fix bad merge on new ticket by staff forms: Show uneditable fields on new ticket by staff oops: Fix bad merge on client ticket view
-
- Dec 09, 2014
-
-
Peter Rotich authored
The commit also renames some fields in department table.
-
- Dec 08, 2014
-
-
Jared Hancock authored
-