Skip to content
Snippets Groups Projects
  1. Jun 22, 2015
  2. May 27, 2015
    • Jared Hancock's avatar
      file: Allow different names for duplicated content · 3bbe2933
      Jared Hancock authored
      This patch (which needs further development), introduces an extra field to
      the %attachment table to store a file's name, in the event that two files
      with the same content are stored in the database with differing names. In
      such a case, the name is stored in the %attachment table. This allows the
      attachment to specify a different name each time the same file is attached
      to something in the system.
      3bbe2933
  3. May 20, 2015
  4. May 13, 2015
  5. Apr 10, 2015
  6. Mar 03, 2015
  7. Feb 10, 2015
  8. Jan 12, 2015
  9. Dec 11, 2014
  10. Dec 10, 2014
    • Jared Hancock's avatar
      oops: Fix numerous, small issues introduced in merges · c5823545
      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
      c5823545
  11. Dec 08, 2014
  12. Sep 26, 2014
  13. Aug 29, 2014
    • Jared Hancock's avatar
      forms: Add media to widgets · 4d861025
      Jared Hancock authored
      This will allow for more complex widgets to be added as plugins which
      include css and javascript media files without manually adding header or
      footer lines.
      4d861025
  14. Oct 14, 2013
  15. Oct 09, 2013
    • Jared Hancock's avatar
      f7384359
    • Jared Hancock's avatar
      Completion of dynamic forms concept · 43b74f4a
      Jared Hancock authored
      Moved to an initial form which specifies the ticket's priority and issue and
      changed the rendering to render things properly. Now the user can decide
      where priority shows on the client side, and the priority privacy setting is
      placed in the dynamic form wizard.
      
      The standard form is added to every ticket without option. Extra forms can
      be defined and associated with help topics which can additionally be added
      to tickets upon creation. This allows for standardization of the dynamic
      data location for searches and filtering.
      
      Implemented advanced search for dynamic data. Along with reinstating the
      basic ticket search on keywords
      
      Implemented ticket filtering on dynamic data for both keyword searches as
      well as searches for special fields (drop-down lists, etc.)
      
      Phone number for users is now completely optional
      43b74f4a
    • Jared Hancock's avatar
      Dynamic data for osTicket · 9e75169e
      Jared Hancock authored
      *This is a major redesign / rework of the osTicket base*
      
      This patch drops the concept of static ticket metadata and allows for an
      admin-configurable arbitrary data that is attachable to tickets
      
      The system is architected such that the base osTicket install now comes with
      a "default" form that has fields for subject, name, email, and phone number.
      This form is editable to allow for the addition of arbitrary other fields;
      however, the basic fields must remain in order to be associated with a
      help-topic and attached to a ticket.
      
      This concept can be expanded to allow for arbitrary data associated with
      registered clients or ticket thread items.
      
      Forms are comprised of sections. Sections have a title and instructions
      properties and a list of fields. Fields have various implementations to
      represent different data such as text, long answer, phone number, datetime,
      yes/no, and selections, and are configurable to define the look and feel and
      interpretation of the respective form field.
      
      Dropdown lists are represented as "Dynamic Lists", which are
      admin-configurable lists of items. Dropdowns can be optionally represented
      as Bootstrap typeahead fields.
      
      This also adds the start of a simple ORM which will hopefully be expanded in
      the future to support multiple database platforms. Currently, only MySQL is
      implemented.
      9e75169e
Loading