RT is written in Perl and runs on the Apache and lighttpd web servers using mod_perl or FastCGI with data stored in either MySQL, PostgreSQL, Oracle or SQLite. It is possible to extend the RT interface using plug-ins written in Perl.5
Jesse Vincent, while enrolled at Wesleyan University in 1994, worked for Wesleyan's computing help desk and was responsible for improving the help desk and residential networking software infrastructure. This task included setting up a ticketing system for the help desk. Initially he set up a Linux server to run "req",6 but later he identified that the command line interface was limiting usage. Over the next two years he created and maintained WebReq, a web based interface for req written in Perl. Eventually the req portions were removed and what was left became RT version 1.0. A complete rewrite occurred for RT version 2.0 when Jesse started to work on RT full-time in 2001 and founded Best Practical Solutions. RT was used by Perl's CPAN, but because of declining use, a sunset date of March 1, 2021, was announced at the Perl NOC on December 4, 2020. rt.cpan.org will sunset on March 1st, 2021. Following a pushback from the developer community, a company was contracted to take over the hosting. rt.cpan.org to remain online.
Organizations of all sizes use Request Tracker to track and manage workflows, customer requests, and internal project tasks of all sorts. Among other things, RT offers custom ticket lifecycles, seamless email integration, configurable automation, and detailed permissions and roles.
RT has many ways to highly customize creating and updating tickets, owners, dependencies, custom everything, and workflows. A web interface is available for both logged in users and guest/customer/end users. Template callbacks allow the modification of the software's web pages without requiring extensive knowledge.
Seamless email integration is another primary interface to RT and is often the only interface many guest users see. The email system includes support for auto-responses, attachments, and full customization of all the rules which govern email. Emails are stored in RT as correspondence on a ticket, and the software can make a distinction between public replies and private comments to show them as appropriate.
A basic REST-like API and a command-line tool are also provided as another way to interact with RT.
Rich, Amy (June 2003). "RT: Request Tracker, Part 1". Sun Microsystems. Archived from the original on 2009-11-15. https://web.archive.org/web/20091115131232/http://www.sun.com/bigadmin/features/articles/req_track_1.jsp ↩
"RT FAQ: What is RT?". Archived from the original on 2016-04-10. Retrieved 2015-08-10. Request Tracker (RT) [...] is available under the terms of the GNU General Public License (GPL). https://web.archive.org/web/20160410230621/http://requesttracker.wikia.com/wiki/FAQ#General ↩
"RTIR: RT for Incident Response". Retrieved 2015-08-10. ready out of the box for your CERT or CSIRT to use https://bestpractical.com/rtir/comparison.html ↩
"REQUEST TRACKER INCIDENT RESPONSE (RTIR) SOFTWARE TO BE UPGRADED AND EXPANDED" (PDF). TERENA. 2005-10-05. Retrieved 2015-08-10. https://www.terena.org/news/archive/2005/news-rtir.pdf ↩
Evard, Rémy (September 1994). "Managing the Ever-Growing To Do List". USENIX. Retrieved 2015-08-10. https://www.usenix.org/conference/lisa-viii/managing-ever-growing-do-list ↩
"RTFM: The RT FAQ Manager". Archived from the original on 2015-09-06. Retrieved 2015-08-10. https://web.archive.org/web/20150906074958/https://bestpractical.com/rtfm/ ↩
"GitHub - bestpractical/rt-extension-nhd". GitHub. 2011-08-10. Retrieved 2016-05-06. https://github.com/bestpractical/rt-extension-nhd ↩