- Apr 24, 2014
-
-
Peter Rotich authored
Users with edit permission should be able to change ticket owner in line.
-
- Feb 27, 2014
-
-
Jared Hancock authored
-
- Feb 25, 2014
-
-
Peter Rotich authored
Join to staff/user tables to get current name when fetching thread entries.
-
- Feb 03, 2014
-
-
Peter Rotich authored
-
- Jan 20, 2014
-
-
Peter Rotich authored
Include collaborator tickets on search by user.
-
- Jan 17, 2014
-
-
Peter Rotich authored
The concept of extid is being retired to pave-way for customizatable ticket numbers.
-
- Jan 15, 2014
-
-
Peter Rotich authored
-
- Jan 10, 2014
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Dec 18, 2013
-
-
Peter Rotich authored
-
- Dec 17, 2013
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Dec 16, 2013
-
-
Jared Hancock authored
HTML does not allow nested <p> tags. Therefore the user warning was not correctly hidden with the rest of the user change confirmation message.
-
- Dec 11, 2013
-
-
Peter Rotich authored
Replace phone number on ticket owner update
-
Jared Hancock authored
Displaying field values on various pages and dialogs could result in cross site scripting exploits. Fixes osTicket/osTicket-1.8#296
-
Jared Hancock authored
Previously, the user information could only be modified on the ticket-view page. For instance, if creating a new ticket for a user, no new information could be added or modified on the user until after the ticket was created Fixes osTicket/osTicket-1.8#281
-
- Dec 10, 2013
-
-
Jared Hancock authored
Change thread entry title bar to use more flexible layout using div's and span's in hopes of avoiding unnecessary wrapping -- especially in the poster name column..
-
- Nov 27, 2013
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Nov 26, 2013
-
-
Peter Rotich authored
-
Peter Rotich authored
-
Peter Rotich authored
support
-
Peter Rotich authored
Unpack user data for filtering purposes for staff created tickets
-
Peter Rotich authored
-
Peter Rotich authored
-
Peter Rotich authored
Add ability to change ticket owner on ticket view Add get last updated date to user class
-
- Nov 15, 2013
-
-
Peter Rotich authored
-
- Nov 14, 2013
-
-
Jared Hancock authored
-
- Nov 12, 2013
-
-
Jared Hancock authored
* Upgrade to Redactor 9.1.7 * Use a (x) icon from font-awesome for the dialog
-
- Nov 08, 2013
-
-
Jared Hancock authored
-
- Nov 05, 2013
-
-
Jared Hancock authored
Fixes #77
-
- Nov 04, 2013
-
-
Jared Hancock authored
Fixes #65
-
- Nov 01, 2013
-
-
Jared Hancock authored
Also ensure that the ticket thread is displayed in a <div> container as some browsers seems to frown upon <iframe>s in <td> elements Fixes #75
-
- Oct 21, 2013
-
-
Jared Hancock authored
-
Jared Hancock authored
-
- Oct 09, 2013
-
-
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 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 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.
-
Jared Hancock authored
Process inline attachments in thread entry and support inline images in piped emails Support inline images across the system, with draft support Migrate to a single attachment table That way we don't need a new table for everything we need to attach an inline image to (like a signature, for instance) Add richtext support for internal notes Implement images on site pages * Image paste in Redactor * Make non-local images optional * Placeholder for non-local images * Fix local image download hover * Don't re-attach inline images
-
- Sep 13, 2013
-
-
Jared Hancock authored
This is safe now, because the title is appropriately encoded in class.thread.php/ThreadEntry::create() Fixes #567, #718
-