These systems often encompass resource allocation, time accounting, priority management, and oversight workflow in addition to implementing a centralized issue registry.
[3] A ticket element, within an issue tracking system, is a running report on a particular problem, its status, and other relevant data.
These tickets are called so because of their origin as small cards within a traditional 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 user's 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.
In bug trackers, issues are generally quality or feature related with respect to a codebase (which is inherently a project management setting) whereas in generalized issue tracking systems, the tickets are often service-related or relationship-based, with closer ties to customer relationship management (CRM) concerns.