- Nov 15, 2014
-
-
Jared Hancock authored
This helps in long UTF-8 characters as the bytes were previously counted and the width of the characters was assumed to correlate with the count of the bytes in the text. This method allows the browser to calmly truncate the text according to the available space in the page where the text is rendered.
-
- Oct 27, 2014
-
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
- Oct 26, 2014
-
-
Jared Hancock authored
-
- Oct 10, 2014
-
-
Jared Hancock authored
Compare the database `state` field rather than the admin editable status name.
-
- Oct 09, 2014
-
-
Jared Hancock authored
Also fix a crash when re-rendering the new ticket by staff page after a validation error.
-
- Oct 07, 2014
-
-
Jared Hancock authored
Since users can already log in via their email address, offer a friendly error message when agents configure the user name to be an email address.
-
Jared Hancock authored
Footer should not be in #pjax_container, because the footer is not rendered for non PJAX requests.
-
- Oct 02, 2014
-
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
- Sep 29, 2014
-
-
Jared Hancock authored
* Use the title of "Information" with internal tag of "info" * Add "Visibility" column to UI and retire "Required" and "Internal" columns * Add visibility selection to new fields and show visibility to the user information fields when displayed on the ticket details form * Make the visibility settings translatable * Use constants internally for visibility configuration detection * Use a larger input when managing the information HTML content * Fix validation errors for new fields * Enforce new field name uniqueness * Enforce new field name character validation
-
- Sep 26, 2014
-
-
Jared Hancock authored
-
Peter Rotich authored
Improve info display & formatting Only show 8 chars of the last commit
-
Peter Rotich authored
-
- Sep 24, 2014
-
-
Peter Rotich authored
Consider current status settings to determine if a ticket is reopen-able Show a warning on staff's ticket view if the ticket is not reopen-able
-
Peter Rotich authored
This will allow administrator to indicate if end users are allowed to reopen tickets in a particular closed status.
-
- Sep 19, 2014
-
-
Peter Rotich authored
This is necessary to avoid confusion vs. closed state.
-
Jared Hancock authored
Also fix crash if the [name] of a widget element started with a digit character.
-
Jared Hancock authored
This allows fields to specify a visibility constraint that will be evaluated in real time in the browser to automatically show and hide fields that should be hidden based on values of other fields in the same form. Validation is not performed on fields server-side if they are considered invisible when submitted.
-
- Sep 10, 2014
-
-
Jared Hancock authored
-
Peter Rotich authored
Redirect to tickets listing page when a ticket is resolved or closed via status change.
-
Peter Rotich authored
Show different messages and placeholder on ticket(s) deletions
-
- Sep 09, 2014
-
-
Jared Hancock authored
-
- Sep 08, 2014
-
-
Jared Hancock authored
-
- Sep 02, 2014
-
-
Jared Hancock authored
Furthermore, revamp the __cdata system to better support multiple selection fields. Drop the `.._id` fields and use a coalesce of the ID value of the entry value or the entry value itself. For JSON backed fields, strip some JSON characters to result in a comma-separated list. The search engine now uses MySQL FIND_IN_SET to analyze a search selection in advanced searches. Also, interaction with the MySQL full text search backend is fully supported.
-
Jared Hancock authored
-
Jared Hancock authored
-
Jared Hancock authored
-
- Sep 01, 2014
-
-
Jared Hancock authored
-
Peter Rotich authored
Make the error message clear
-
Jared Hancock authored
-
Peter Rotich authored
-
Peter Rotich authored
-
- Aug 30, 2014
-
-
Jared Hancock authored
-
- Aug 29, 2014
-
-
Jared Hancock authored
-