Alumni Tracking System Essay Example for Free

Alumni Tracking System Essay An issue tracking system (also ITS, trouble ticket system, support ticket or incident ticket system) is a computer software package that manages and maintains lists of issues, as needed by an organization. Issue tracking systems are commonly used in an organizations customer support call center to create, update, and resolve reported customer issues, or even issues reported by that organizations other employees. An issue tracking system often also contains a knowledge base containing information on each customer, resolutions to common problems, and other such data. An issue tracking system is similar to a bugtracker, and often, a software company will sell both, and some bugtrackers are capable of being used as an issue tracking system, and vice versa. Consistent use of an issue or bug tracking system is considered one of the hallmarks of a good software team.[1] A ticket is an element contained within an issue tracking system which contains information about support interventions made by technical support staff or third parties on behalf of an end-user who has reported an incident that is preventing them from working with their computer as they would expect to be able to. Tickets are commonly created in a help desk or call center environment. Typically the ticket will have a unique reference number, also known as a case, issue or call log number which is used to allow the user or support staff to quickly locate, add to or communicate the status of the users issue or request. These tickets are so called because of their origin as small cards within a typical wall mounted work planning system when this kind of support started. Operators or staff receiving a call or query from a user would fill out a small card with the users details and a brief summary of the request and place it into a position (usually the last) in a column of pending slots for an appropriate engineer, so determining the staff member who would deal with the query and the priority of the request.