Skip to main content
Our Tech Ideas

All about ticketing tools for DBA?

Ticketing tools

Ticketing tools improves communications tracking whatever is happening in the environment, reporting that what has happened within the specified duration. A Ticket is an element contained within an issue tracking system that 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 user’s issue or request.

The Tools used by various companies are

  • BMC Remedy
  • Freshdesk
  • Salesforce
  • Wipro E-Desk
  • Wipro Virtual Ticket
  • Inbuilt Ticketing Tool
  • Help Desk
  • SMAX Microfocus
  • TCS Service Control
  • Jira Service Desk
  • Pagerduty
  • Freshservice
  • Spiceworks
  • Zendesk
  • ServiceNow
  • Zoho Desk
  • Bitrix24

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 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.
  5. After the issue has been fully addressed, it is marked as resolved in the issue tracking system.The problem may not have been fully corrected, yet it will still be marked as resolved. The problem may be by-design, a known issue, or have a suitable workaround.

A Run Book Automation process that implements best practices of this workflow and increases IT personnel effectiveness is becoming very common.