1. 20 Sep, 2014 2 commits
  2. 04 Jun, 2014 1 commit
  3. 20 May, 2014 1 commit
  4. 16 May, 2014 1 commit
  5. 22 Apr, 2014 1 commit
  6. 01 Apr, 2014 2 commits
  7. 08 Jan, 2014 1 commit
    • Jared Hancock's avatar
      Fix possible serious errors in dynamic form fields · 7e7c4cf0
      Jared Hancock authored
      Fix dropping of materialized view when variable name is changed
      Ensure view exists before merging updates
      Prevent possible sql injection error in field name used in the materialized
      Prevent possible xss error in the display of the field label and variable
      name in the admin panel.
  8. 11 Dec, 2013 1 commit
  9. 27 Nov, 2013 2 commits
  10. 25 Nov, 2013 1 commit
  11. 22 Nov, 2013 1 commit
  12. 16 Nov, 2013 1 commit
  13. 12 Nov, 2013 1 commit
  14. 05 Nov, 2013 2 commits
  15. 09 Oct, 2013 7 commits
    • Jared Hancock's avatar
      Rebase onto feature/html-thread · 9e4e35d7
      Jared Hancock authored
    • Jared Hancock's avatar
    • Jared Hancock's avatar
      Fixup the installer · e055cc21
      Jared Hancock authored
      Fixup several minor bugs concerning initial experience
    • 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
    • Jared Hancock's avatar
      Move client information to separate formset · 53666db6
      Jared Hancock authored
      This moves client information like name and email address out of the general
      dynamic forms data for a ticket. It really paves the way for the first-class
      user of the future.
    • Jared Hancock's avatar
      Rebase form sections to forms and remove form sets · 59c219f4
      Jared Hancock authored
      Previously, form sections were grouped into form sets for reusability. This
      patch drops the form sets and makes form sections the new "forms".
      Eventually a section-header field will be added that technically does not
      add any dynamic data to the form, but allows for the same feature as having
      a form set with multiple sections.
    • 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