SimpleTicket on Digg!
SimpleTicket found its way onto Digg (thanks Brian!). Looks like we are up to 480 ‘diggs’ Woot! Most of the comments are positive. Remember, this is the first ‘release’ it will get better. What do you expect from the first Ruby on Rails ticketing system? Perfection? Ha! Help get the word out and Digg it! Just click here and then press Digg It!
SVN Access!
Thanks to Alex Leverington, you may:
svn co svn://project.simpleticket.net/trunk
This is the same code that was released Saturday. I am working right now on the Customers screen (to AJAX / Prototype-ify the view)… and will post that once I am happy with it.
Thanks!
Forum tab…
I put up a quick phpBB forum on one of the other servers. The forum tab at the top of the site should take you there. I am looking for feedback, concerns, help, love…
Would you like Coder A or Coder B?
This is likely one of the funniest things that has ever happened to me. Adam Keyes shows up, dressed in the exact opposite shirt to what I was wearing the day of the Mashpit session Chris Messina held. As we were two of the three programmers there (Chris St.John was the other) Adam pointed out that we couldn’t be on the same team as we might negate each other.
I hadn’t even noticed before then. 
Setting up SimpleTicket
Ok, this is kinda freeform since I’ve never written anything like it before…
The system comes in two directories. The first, tt/, contains the code to run the client side of the application. The second, stadmin/, contains the administration section of the system.
The simplest way to install SimpleTicket is to start with a clean Linux box, and follow some of the simple installs for Rails / Ruby / Lighttpd / MySQL that you can find here. Point the lighttpd / apache configs to your directories running both tt and stadmin.
In the stadmin directory structure, under db/, there is a file called ttdb.sql. This is the database schema for the system. Import this into MySQL to setup the database.
Once your database is setup, you will have to manually add a Customer to the customers table in the database. I am working this week on an administration screen for this to help in the process (I know, HURRY KEVIN! 
) . Then, test the tt system by creating an account. Client accounts are created by entering an e-mail address whose domain matches the email address of the customer account you created.
Here is a quick breakdown of the terminology/tables used…
| Term | Table | Function |
|---|---|---|
| Customer | customer | Company information - the general grouping of users |
| User | users | Both persons that you support and the engineers that support them - you can add engineers by logging into the stadmin system and then going to http:///account/signup |
| Ticket | tickets | Ticket master table - contains references to all of the other parts of a ticket (Journals, Assignees, Priorities, Statuses) |
| Journal | journals | Journal table - contains all changes done to a ticket |
| Priority | priorities | Assignable priorities table - edit this table to change how you want your priorities worded - ranked from 1 = highest to 6 = lowest |
| Status | statuses | Statuses table - Open, Closed, Pending, Contacted |
Take a look at the workflow posts on how this all meshes. If you need more help, I may put up an IRC channel.
- Kevin