SimpleTicket 2.0 (first look)
Here are draft screenshots of SimpleTicket 2.0 (full size versions here oh and here is the ZIP of the PDFs - more recent than these pics):
This is the Tickets:pending tickets view. When tickets hit the system they first show up here. In our install they turn red when they reach 30 minutes without any action. If a user is contacted, but they are not available we set their ticket as “contacted” and it turns green. If a green ticket reaches 24 hours without an update it will turn red. The slider allows the user to select the number of items in the current screen view (20-ALL). In he right column there are alerts, stats, our blog and the key.
This is the Tickets:pending tickets view with detail shown on the ticket. If you click on the text it will expand in a smooth ajaxian way. The ticket detail offers a link to the client’s wiki (i.e. our internal system), quick access to the users email address and detail from the ticket. There are two options 1) take it (i.e. put it in your my ticket view) and 2) close view (to make it all go away). Once the ticket is ‘taken’ the detail and ticket disappears and moves to the engineer’s “my ticket” view. You are then taken to your “my ticket” page.
This is the Tickets:my tickets view with detail shown on the ticket. This is what you would see if you just took a ticket from the pending que. This screen offers the engineer three options. First, they can view the history of the ticket (this will be explained in another view), they can do a quick update (limited) or update the ticket. There is no cancel or close as each time a ticket is opened you MUST update it. The action field is a drop down, time spent is in minutes and must be filled in to be able to click the update ticket number. Notify allows the engineer to send a copy of the update to the user. Now engineers can tag their tickets. Priority is now only two options: low or high. Difficulty is associated with the issue: level 1, level 2, level 3. Next you can reassign the ticket in the same action using the drop down field. Finally, you can attach a file to the update.
This is the Create Ticket ajax pop-up. Almost every page has a “create ticket” button. We simplified the process of creation by putting everything on one screen accessible from anywhere. Now you use a drop down to select the customer and then the user. Engineers can set priority, notify user that they created the ticket, add tags, take the ticket once it is created (versus having to go to the pending view to take it).
This is the Tickets:all tickets view. You can think of this as a search page. There will be an anvanced search tab, but for now this offers a fairly powerful search function. The engineer can view “all tickets” in this view by using the slider (20 to ALL) on one page. The engineer can quickly see the age, the customer, user, subject, last update, priorty and engineer. He can choose to update the ticket or get the ticket’s history.
The most exciting feature on this tool is the combined filter and search function. Engineers can now filter by engineer, customer, status and if they choose add a search term to that filter. The idea is to start allowing engineers to ’save’ filtered searches for future use. There are also buttons for the most requested filters.
This view is the Ticket History view. Each time a ticket is created and updated that information is available on the ticket history page. When you click a ticket’s history you get a browser pop-up (yes a pop-up) that can easily be printed. You can view it while you still have the ticket in update mode. Very simple. The updates are in order of most recent update.
This is the Customer view. Engineers can create a new customer, get information about a current customer or edit that information. Each line has a link to the client’s website, a link to a map, a link to the wiki and an edit button.
This is the Customer detail view. Engineers can click on the text of a customer and a nice ajaxian effect will reveal this panel. The engineer can see basic information about the client including contact information, user info and basic stats.
This is the view when you click the ‘edit’ button for a customer. The information previously entered is shown (not in the picture above) and an engineer can edit it.
Alternatively, engineers can create new customers using the same screen (with a different title).
This view is of the Statistics:user stats view. First the engineer would select the customer and then a list of users would be shown. The slider is missing from this page - this is an error.
This view is of the Statistics:engineer stats view. Enough said.
This is the view of the Statistics:customer metrics view.
This is the Adminstrative:engineer view. Both current and former engineers are listed with contact information. Engineer information can be edited from this view.
This is the Administrative:engineer view with edit detail shown. Here you can edit an engineers information, change their password, select their status and set their access level.
This is the add engineer view (the nav is a little off - an older version). Just like the edit section except that you must fill in all of the data and upload a picture.
This is the administration:alerts/notices/settings view. This page has not been fully developed, but it will allow for global settings, editing of notices and editing of alerts.
This is the adminstration:alerts/notices/settings view with editing view. You can edit the email messages and alerts from this view.
That is it for now.
SimpleTicket Conference Call (10am CDT)
This week’s conference call will be a summary of what will be committed to the trunk for May’s release as well as discussion with regard to beginning development of the next version of SimpleTicket. If there is a topic you’d like to add simply join us at 10:00am by calling 214.550.3540. You can also join the conference call via SIP (VoIP/Free) by dailing 1-747-622-8399 (sipphone.com) via Gizmo.
Update: The podcast has been posted for this weeks conference call - listen to it here.
Major Topics for Today’s Call:
- Organizations (crm) code
- Features moving to the next release
- SimpleTicket May Release
Features to add:
- Supporting Multiple Email domains
- Filtered tickets view (done - needs commit)
- Using ticket numbers
Major bugs to fix:
- RSS queries for all feed links
Little things which need tweaking:
- add confirmations to ticket reassignments
- genera ui design
- login not downloading domains
- remove redundant create ticket link
- threaded mailer (rails 1.0 broke our current implementation)
Features that could move move to next release:
- Basic Search
- CRM
- Projects
- Rich Text
SimpleTicket Updates
If you’ve just run across SimpleTicket or have recently tried to access the demo we’ve made a few changes around the site. Here is an update on where everything is at:
Mailing list:
http://project.simpleticket.net:81/mailman/listinfo/simpleticket
You can browse the current dev source at
http://project.simpleticket.net/repository/browse/branches/developers/masukomi
To check out:
svn co svn://project.simpleticket.net/branches/developers/masukomi
To report bugs:
http://project.simpleticket.net/tickets/new
Demo for engineer side: http://dev.simpleticket.net/admin
Demo for client side: http://dev.simpleticket.net/
Username is admin and the password is password
SimpleTicket Conference Call
Today’s conference call will be an update on the May simpleticket release and a quick discussion of what’s left todo. In addition we will be discussing Peter Boling’s April 22nd enhancements to SimpleTicket.
You can track the progress of tickets via the RSS feed.
See below for a quick list of what’s left todo:
T = Ticket number, C = Changeset number
Features:
T30: Multiple E-Mail Domains
T29: RSS - create methods for all queries
User Interface:
???:Â General UI / design cleanup for login, prefs, admin, etc.
T27: update login system to ajax domain instead of downloading a list
T26: add confirmation to ticket reassignments
T25: Change organizations back to “Customers” (in views)
Bugs:
T24: values in pending ticket view / newlines in pending ticket view
T23: update text after ticket is taken doesn’t post
T21: “Close” image for ticket popup is missing
T22: when there are no users for a company, create ticket freaks out
DONE (no commit = still testing):
T20/C219: RSS - links need consistency (need to create a few queries)
T19/C220: fixup the authentication (find out why it bombs on /admin on
our server)
T32: Ability to filter tickets by engineer and/or status
T31: thread mailers
T28: *Basic Search
SimpleTicket installs in China?
Looks like there is going to be a SimpleTicket install in China. Check it out here.