
Request Tracker
Request Tracker (RT) is a highly customizable request tracking and workflow automation system written in Perl. It is extensively used by IT departments, customer support teams, and development organizations to manage tasks, issues, and communications with users effectively. RT provides a robust framework for handling diverse workflows, from simple helpdesk tickets to complex project management and bug tracking.
About Request Tracker
Request Tracker (RT) is a powerful and flexible open-source system designed for managing and automating workflows based on requests. At its core, RT is a sophisticated ticketing system that can be adapted to a wide range of use cases beyond traditional IT support. Its strength lies in its extensive customization options, allowing organizations to tailor the system to their specific operational needs.
Key features include a comprehensive set of tools for tracking requests from their inception to resolution, managing relationships between related tickets, and automating responses and actions based on predefined conditions. RT's workflow engine allows administrators to define complex processes, ensuring that tasks are handled consistently and efficiently.
The system offers multiple channels for request submission, including email, web forms, and integration with other systems. Its robust email handling capabilities are particularly noteworthy, allowing seamless conversion of emails into tickets and management of communication threads within the system. Advanced features like customizable queues, service level agreements (SLAs), and reporting enable organizations to monitor performance and identify bottlenecks.
RT is highly extensible through its comprehensive API and plugin architecture, allowing for integration with existing tools and development of custom functionalities. It also includes features for team collaboration, time tracking, asset management, and a built-in wiki for documentation and knowledge base creation. Its open-source nature means it is continuously improved by a vibrant community, and commercial support is available from Best Practical Solutions.
Pros & Cons
Pros
- Extremely customizable and adaptable to various workflows.
- Powerful email integration for ticket creation and communication.
- Open-source with a strong community and available commercial support.
- Comprehensive reporting capabilities.
- Highly extensible through plugins and API.
Cons
- Can have a steep learning curve for administration.
- User interface may feel less modern compared to some commercial alternatives.
- Requires technical expertise for initial setup and complex configurations.
- Relies heavily on configuration rather than out-of-the-box simplicity.
What Makes Request Tracker Stand Out
Highly Customizable
Extensive configuration options allow tailoring the system to a wide variety of workflows and business needs.
Open-Source Flexibility
Provides transparency, control, and the ability to modify or extend the system freely.
Robust Email Integration
Industry-leading email handling capabilities for seamless ticket creation and communication management.
Features & Capabilities
23 featuresExpert Review
Request Tracker (RT) Software Review
Request Tracker (RT) is a well-established and highly regarded open-source request tracking system. Often categorized as a helpdesk or issue tracking system, RT's true power lies in its flexibility and ability to be shaped into a workflow management tool for virtually any process involving requests or tasks.
Core Functionality and Workflow
At its heart, RT excels at capturing, organizing, and tracking requests. These requests, or tickets, can originate from various sources, most commonly email, but also through web forms, APIs, and even command-line interfaces. Once a ticket is created, it enters a queue, where it can be assigned to individuals or groups, have its status updated, and be enriched with context and communications.One of RT's most compelling features is its workflow engine. Unlike many rigid ticketing systems, RT allows administrators to define states and transitions for tickets, creating custom workflows that mirror an organization's specific processes. These workflows can be simple, like 'Open -> Resolved -> Closed', or complex, involving multiple stages, approvals, and conditional transitions. Customizable triggers further enhance this by enabling automated actions based on specific events, such as sending notifications, assigning tickets, or modifying ticket properties. This level of workflow customization is a significant advantage for organizations with unique operational requirements.
Customization and Extensibility
RT's architecture is built for customization. Beyond workflows and triggers, virtually every aspect of the system can be configured, from custom fields to user roles and permissions. This allows organizations to collect and track the exact information they need for each type of request. For developers and technically inclined administrators, RT offers a comprehensive API and a robust plugin system, enabling integration with other software and the development of custom features. This extensibility is crucial for organizations that need RT to interact with existing systems or have specialized needs that are not met by the core functionality.User Interface and Experience
Historically, RT's user interface has been functional but arguably less polished than some modern, commercially-developed platforms. While it provides all the necessary tools and information, navigating the interface can sometimes feel less intuitive for new users. However, recent versions have seen improvements in this area, with ongoing efforts to modernize the look and feel. Despite this, the power and depth of configuration come with a certain level of complexity, meaning that initial setup and ongoing administration require a moderate level of technical expertise. For end-users interacting with the system to submit or track their requests, the experience is generally straightforward, particularly through email.Beyond Helpdesk
While RT is an excellent helpdesk system, its capabilities extend far beyond IT support. It is successfully used in various domains:- Bug Tracking: Developers can track, prioritize, and manage software defects.
- Project Management: Simple project tasks can be broken down and tracked.
- Customer Service: Managing customer inquiries, feedback, and service requests.
- Incident Management: Tracking and resolving system incidents.
- HR Processes: Managing internal requests like onboarding or leave requests.
The ability to create different queues and workflows for these distinct use cases makes RT a versatile tool for consolidating various tracking needs within a single platform.