- Aug 13, 2012
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Jul 30, 2012
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Jul 21, 2012
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Jul 16, 2012
-
-
Peter Rotich authored
-
- Jul 09, 2012
-
-
Jared Hancock authored
And rearrange files to work with the new layout for the finalized upgrader
-
Peter Rotich authored
-
- Jul 05, 2012
-
-
Peter Rotich authored
-
- Jun 30, 2012
-
-
Jared Hancock authored
-
- Jun 28, 2012
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- Jun 26, 2012
-
-
Peter Rotich authored
-
- Jun 23, 2012
-
-
Jared Hancock authored
-
- Jun 18, 2012
-
-
Peter Rotich authored
-
Jared Hancock authored
-
Jared Hancock authored
Allow staff members the ability to select a default paper size which will be used in printing tickets via PDF. In the future, this may be overridden per ticket by a dialog box at print time.
-
- May 13, 2012
-
-
Peter Rotich authored
-
Peter Rotich authored
-
- May 10, 2012
-
-
Peter Rotich authored
-
- Apr 28, 2012
-
-
Peter Rotich authored
-
- Apr 26, 2012
-
-
Jonathan Putney authored
Updating main.inc.php: File did not include a define statement for TICKET_EMAIL_INFO_TABLE used by include/class.ticket.php
-
Peter Rotich authored
-
- Apr 25, 2012
-
-
Peter Rotich authored
-
- Apr 23, 2012
-
-
Jared Hancock authored
-
Jared Hancock authored
-
- Apr 13, 2012
-
-
Peter Rotich authored
-
- Apr 09, 2012
-
-
Jared Hancock authored
Replace the ticket_{message,response,note} tables with a single ticket_thread table that will contain data for all three current message types. This simplifies much of the ticket thread code and paves the way for other types of messages in the future.
-
- Apr 06, 2012
-
-
Jared Hancock authored
Track assigned department, team, staff, and help topic when the ticket event occurs. This will greatly help in correlation of various reports and queries Also start plowing the way toward incremental database updates using a patching technique. The hash of the main install SQL script for a respective database will be used to track the signature of the database currently. The signature will be stored in %config::schema_signature, and the main.inc.php script can simply check the value in the schema against the value known to the source code to be the signature the code expects. Should the two signatures differ, patches in the setup/inc/sql/patches folder should exist and be executed to assist in incrementally upgrading the database to the new-current schema version.
-
- Apr 02, 2012
-
-
Peter Rotich authored
-
- Mar 22, 2012
-
-
Peter Rotich authored
-
- Mar 19, 2012
-
-
Jared Hancock authored
-