Issue tracking system

Last updated

An issue tracking system (also ITS, trouble ticket system, support ticket, request management or incident ticket system) is a computer software package that manages and maintains lists of issues. [1] Issue tracking systems are generally used in collaborative settings, especially in large or distributed collaborations, but can also be employed by individuals as part of a time management or personal productivity regimen. These systems often encompass resource allocation, time accounting, priority management, and oversight workflow in addition to implementing a centralized issue registry.

Contents

Background

In the institutional setting, issue tracking systems are commonly used in an organization's customer support call center to create, update, and resolve reported customer issues, or even issues reported by that organization's other employees. A support ticket should include vital information for the account involved and the issue encountered. [2] 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". [3] A ticket element, within an issue tracking system, is a running report on a particular problem, its status, and other relevant data. They are commonly created in a help desk or call center environment and almost always have a unique reference number, also known as a case, issue or call log number which is used to allow the user or help staff to quickly locate, add to or communicate the status of the user's issue or request.

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.

The shared conceptual foundation between issue tracking systems and bugtrackers is that a valid issue must be amenable to a decisive resolution (such as "completed", "fixed", or a group consensus that the issue is not worth solving, such as "not a problem" or "won't fix"); that each issue is unique (duplicate problem reports are in most cases promptly amalgamated into a single active issue or ticket); and—beyond the screening stage—that there is precisely one person assigned formal responsibility to move the issue forward (this formal baton will often bounce around many times as the issue evolves). 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. [4]

Issues

Issues can have several aspects to them. Each issue in the system may have an urgency value assigned to it, based on the overall importance of that issue. Low or zero urgency issues are minor and should be resolved as time permits. Other details of issues include the customer experiencing the issue (whether external or internal), date of submission, [5] detailed descriptions of the problem being experienced, attempted solutions or workarounds, and other relevant information. Each issue maintains a history of each change.

Functions

Issue-tracking systems fulfill different functions, in particular:

Workflow

An example scenario is presented to demonstrate how a common issue tracking system would work:

  1. A customer service technician receives a telephone call, email, or other communication from a customer about a problem. Some applications provide built-in messaging system and automatic error reporting from exception handling blocks.
  2. The technician verifies that the problem is real, and not just perceived. The technician will also ensure that enough information about the problem is obtained from the customer. This information generally includes the environment of the customer, when and how the issue occurs, and all other relevant circumstances.
  3. The technician creates the issue in the system, entering all relevant data, as provided by the customer.
  4. As work is done on that issue, the system is updated with new data by the technician. Any attempt at fixing the problem should be noted in the issue system. Ticket status most likely will be changed from open to pending.
  5. After the issue has been fully addressed, it is marked as resolved in the issue tracking system.

If the problem is not fully resolved, the ticket will be reopened once the technician receives new information from the customer. A Run Book Automation process that implements best practices for these workflows and increases IT personnel effectiveness is becoming very common.

Use in different sectors

Government

Some government services use issue tracking system to keep track of issues and display them to the public. Issue tracking systems may show all tasks still to be done by the government (in a waiting queue), finished tasks, tasks in progress, order sequence, etc.[ citation needed ] Finished tasks can also be foreseen with the report, showing what exactly has been done on the issue.[ citation needed ]

Issue tracking systems are for instance used to track which legislative bills are up for voting and the outcome of them. [6]

Transport and infrastructure issues (i.e. obstructions on roads, complains, ...) can also be filed using issue tracking systems. [7] The issues can then be tackled by the relevant government services.

See also

Related Research Articles

A software bug is an error, flaw or fault in the design, development, or operation of computer software that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. The process of finding and correcting bugs is termed "debugging" and often uses formal techniques or tools to pinpoint bugs. Since the 1950s, some computer systems have been designed to detect or auto-correct various software errors during operations.

In telecommunication, provisioning involves the process of preparing and equipping a network to allow it to provide new services to its users. In National Security/Emergency Preparedness telecommunications services, "provisioning" equates to "initiation" and includes altering the state of an existing priority service or capability.

<span class="mw-page-title-main">Technical support</span> Maintenance service of electronic consumers

Technical support, also known as tech support, is a call centre type customer service provided by companies to advise and assist registered users with issues concerning their technical products. Traditionally done on the phone, technical support can now be conducted online or through chat. At present, most large and mid-size companies have outsourced their tech support operations. Many companies provide discussion boards for users of their products to interact; such forums allow companies to reduce their support costs without losing the benefit of customer feedback.

Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.

A tracking system or defect tracking system is a software application that keeps track of reported software bugs in software development projects. It may be regarded as a type of issue tracking system.

<span class="mw-page-title-main">OTRS</span> Service management software

OTRS is a service management suite. The suite contains an agent portal, admin dashboard and customer portal. In the agent portal, teams process tickets and requests from customers. There are various ways in which this information, as well as customer and related data can be viewed. As the name implies, the admin dashboard allows system administrators to manage the system: Options are many, but include roles and groups, process automation, channel integration, and CMDB/database options. The third component, the customer portal, is much like a customizable webpage where information can be shared with customers and requests can be tracked on the customer side.

Business software is any software or set of computer programs used by business users to perform various business functions. These business applications are used to increase productivity, measure productivity, and perform other business functions accurately.

Information technology service management (ITSM) are the activities performed by an organization to design, build, deliver, operate and control information technology (IT) services offered to customers.

Help desk and incident reporting auditing is an examination of the controls within the help desk operations. The audit process collects and evaluates evidence of an organization's help desk and incident reporting practices, and operations. The audit ensures that all problems reported by users have been adequately documented and that controls exist so that only authorized staff can archive the users’ entries. It also determine if there are sufficient controls to escalate issues according to priority.

<span class="mw-page-title-main">Request Tracker</span> Open source ticket-tracking software

Request Tracker, commonly abbreviated to RT, is an open source tool for organizations of all sizes to track and manage workflows, customer requests, and internal project tasks of all sorts. With seamless email integration, custom ticket lifecycles, configurable automation, and detailed permissions and roles, Request Tracker began as ticket-tracking software written in Perl used to coordinate tasks and manage requests among an online community of users.

<span class="mw-page-title-main">Task management</span> Process of managing a task through its life cycle

Task management is the process of overseeing a task through its lifecycle. It involves planning, testing, tracking, and reporting. Task management can help individuals achieve goals or enable groups of individuals to collaborate and share knowledge for the accomplishment of collective goals. Tasks are also differentiated by complexity, from low to high.

In IBM terminology, a Program temporary fix or Product temporary fix (PTF), sometimes depending on date, is a single bug fix, or group of fixes, distributed in a form ready to install for customers.

Software project management is the process of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.

In management, an action item is a documented event, task, activity, or action that needs to take place. Action items are discrete units that can be handled by a single person.

A virtual help desk allows IT support organizations to virtually deploy IT technicians on demand to support a computer user experiencing technical issues. IT can efficiently manage and allocate global help desk resources, including – most importantly – its personnel, to access any computer to provide support despite the end user or IT rep location. Virtual help desks allow IT reps to virtually access end systems through support sessions where they can diagnose and fix computer issues quickly. This eliminates in-person customer service calls and/or ineffective phone-only tech support sessions, making the help desk more efficient. Another objective of the virtual help desk is to improve IT resource management and save organization's money by increasing IT support efficiencies. Through an enhanced ability to allocate resources, IT organizations have the flexibility to create new ways of using its technical support knowledgebase. This technology usually requires a software implementation and support contract.

Collaborative workflow is the convergence of social software with service management (workflow) software. As the definition implies, collaborative workflow is derived from both workflow software and social software such as chat, instant messaging, and document collaboration.

Marketing automation refers to software platforms and technologies designed for marketing departments and organizations automate repetitive tasks and consolidate multi-channel interactions, tracking and web analytics, lead scoring, campaign management and reporting into one system. It often integrates with customer relationship management (CRM) and customer data platform (CDP) software.

Help desk software is a computer program that enables customer-care operators to keep track of user requests and deal with other customer-care-related issues.

Networked Help Desk is an open standard initiative to provide a common API for sharing customer support tickets between separate instances of issue tracking, bug tracking, customer relationship management (CRM) and project management systems to improve customer service and reduce vendor lock-in. The initiative was created by Zendesk in June 2011 in collaboration with eight other founding member organizations including Atlassian, New Relic, OTRS, Pivotal Tracker, ServiceNow and SugarCRM. The first integration, between Zendesk and Atlassian's issue tracking product, Jira, was announced at the 2011 Atlassian Summit. By August 2011, 34 member companies had joined the initiative. A year after launching, over 50 organizations had joined. Within Zendesk instances this feature is branded as ticket sharing.

Data center management is the collection of tasks performed by those responsible for managing ongoing operation of a data center. This includes Business service management and planning for the future.

References

  1. ↑ Bertram, Dane. The social nature of issue tracking in software engineering Archived 2016-11-08 at the Wayback Machine . Diss. University of Calgary, 2009.
  2. ↑ Murphy, Ian (November 11, 2021). "Ticketing or Bug Tracking System Explained".
  3. ↑ Joel Spolsky (November 8, 2000). "Painless Bug Tracking" . Retrieved 29 October 2010.
  4. ↑ Murphy, Ian (November 11, 2021). "CRM Customer Relationship Management Explained".
  5. ↑ Method and Apparatus for Performing Remote Operations in an Issue Tracking Environment, 2013-08-29, retrieved 2019-04-05
  6. ↑ For example: "Senate Tracker Help – The Florida Senate". flsenate.gov. Retrieved 2021-01-17. "Legislative Search Results". congress.gov. Retrieved 2021-01-17. "GovTrack.us: Tracking the U.S. Congress". govtrack.us. Retrieved 2021-01-17.
  7. ↑ Track progress of a reported road fault or issue
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.