Plone Ticketing System

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

3 comments

Comments 1 - 3 of 3 previous next Post a comment

  • + deanpowers deanpowers 8 months ago
    We plan to move the ticketing system to our new Zope3 based social collaboration application, Z3ext. This means that from within Z3ext it will be possible for users to create tickets about Z3ext support issues. For an extranet, it means that external customers can create tickets about a product or service.
  • + deanpowers deanpowers 3 years ago
    Update: Since this presentation was produced, the ticketing system has been migrated to run on Zope3 and therefore does not require Plone. Also, search has been enhanced through the use of Lucene. The presentation will be updated shortly.



    Dean Powers

    CEO, Gadoz

    email: dean@gadoz.com
  • + guestcc9bd9 guestcc9bd9 3 years ago
    its awsome
Post a comment
Embed Video
Edit your comment Cancel

6 Favorites & 1 Group

Plone Ticketing System - Presentation Transcript

  1. Overview of Gadoz Ticketing System Dean Powers Founder, Gadoz Email: [email_address] November 19, 2006
  2. Presentation Goals
    • Ticketing System Design Goals
    • Target Market
    • Primary Features
  3. Ticketing System Design Goals
    • To Build A Ticketing System that is: Highly Customizable Integrated with Plone CMS Hosted Web Service or Local Server AJAX Enabled UI
  4. Target Market
    • Complex Ticketing Environments Test Labs that Track Jobs and Samples Environments with Complicated Ticket Workflow Need to Charge Customers based on Fixed or Hourly Rates Need to Account for Staff Time Per Ticket Integration into SalesForce.com
  5. Underlying Technology
    • Plone Content Management System (2.51)
    • Zope Application Server (2.10)
    • Python
    • Linux, FreeBSD, Windows, OS X
    Benefits : Open Source, No Licensing Fees, Non-Proprietary
  6. Primary Ticketing System Features
    • Per User Email Notification Policies
    • Public/Private Ticket Comments & Ticket Attachments
    • Staff Time Records for Each Ticket
    • Customizable Ticket Workflow
    • Ticket Sharing with Other Users
    • Incoming Emails Generate Tickets
    • Replies to Emails Become Part of Ticket Comments
  7. Extranet Features
    • Company/Division/User Accounts
    • Tickets Private To Each User
    • Users may Share Tickets with other Users
    • “ Teams” allow groups of users to access tickets
  8. Email Features
    • Users login with Email Address
    • System generates automatic emails based on each users email notification policy
    • Email notification policy can be locked for each user by manager.
  9. Login Features
    • Login using email address (new feature)
    • User ID is separate from email address so users can change email and not affect login
    • Retreive password and reset password feature
    • System Manager can force “strong” passwords as system option. Requires users to select passwords with both letters and numbers.
  10. Ticket Comment Feature
    • Staff and users can add comments to tickets
    • By default, staff comments are internal and not viewable by customers
    • User comments are viewable to staff
    • New comments generate emails to staff and users based on their email notification policy
    • User replies to emails are added to ticket as a comment
  11. Incoming Email
    • Users can create a ticket simply by sending an email to an address configured by site manager.
    • Application looks at “from-to” address to select Company/User
    • Email Subject --->Ticket Title
    • Email Body --> Ticket Description
    • Email Attachments--->Ticket Attachments
    • Benefit to Users: Submit Tickets without logging into Support Site
    • Benefit to Support Organizations: Turn incoming email into tickets
  12. Automatic Emails
    • Emails generated by System include Ticket Number, Title, Description
    • Users/Staff may reply to email and the emailed reply becomes part of Ticket comments
    • Owners are tickets are automatically subscribed to tickets
    • Other members of Company may subscribe to tickets for which they have been given access rights
  13. Licensing Model
    • Hosted Web Application on Gadoz Servers Fixed Monthly Fee + Disk Space or
    • Installed on your server for one-time cost One-Time License Fee + Monthly Support
    Benefits : Begin as Web Application---> Migrate to in-house App
  14. Want to Know More?
    • [email_address]
    • Web Site: http://www.gadoz.com/
    • Chat: Yahoo - [email_address] Jabber - deanpowers@jabber.org AIM - [email_address] ICQ - 339638184
    Benefits : Begin as Web Application---> Migrate to in-house App

+ deanpowersdeanpowers, 4 years ago

custom

12154 views, 6 favs, 2 embeds more stats

Advanced Ticketing System based on Plone CMS

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 12154
    • 12151 on SlideShare
    • 3 from embeds
  • Comments 3
  • Favorites 6
  • Downloads 0
Most viewed embeds
  • 2 views on http://www.apurva.com
  • 1 views on http://www.fachak.com

more

All embeds
  • 2 views on http://www.apurva.com
  • 1 views on http://www.fachak.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories

Groups / Events