Lesson plan
Request Tracker
Request Tracker, commonly abbreviated to RT, is an open source tool for the tracking and management of workflows, customer requests, and internal project tasks. Request Tracker began as ticket-tracking software written in Perl used to coordinate tasks and manage requests among an online community of users. It supports email integration, custom ticket lifecycles, configurable automation, and detailed permissions and roles. RT's first release in 1996 was written by Jesse Vincent, who later formed Best Practical Solutions LLC to distribute, develop, and support the package. RT is open source (FOSS) and distributed under the GNU General Public License. Request Tracker for Incident Response (RTIR) is a special distribution of RT to fulfill the specific needs of CERT teams. It was initially developed in cooperation with JANET-CERT, and in 2006 was upgraded and expanded with joint funding from nine Computer Security Incident Response Teams (CSIRTs) in Europe.
Article summary
Request Tracker, commonly abbreviated to RT, is an open source tool for the tracking and management of workflows, customer requests, and internal project tasks. Request Tracker began as ticket-tracking software written in Perl used to coordinate tasks and manage requests among an online community of users. It supports email integration, custom ticket lifecycles, configurable automation, and detailed permissions and roles. RT's first release in 1996 was written by Jesse Vincent, who later formed Best Practical Solutions LLC to distribute, develop, and support the package. RT is open source (FOSS) and distributed under the GNU General Public License. Request Tracker for Incident Response (RTIR) is a special distribution of RT to fulfill the specific needs of CERT teams. It was initially developed in cooperation with JANET-CERT, and in 2006 was upgraded and expanded with joint funding from nine Computer Security Incident Response Teams (CSIRTs) in Europe.
Key claims
No claims recorded.
Discussion questions
- Summarise the article in your own words. Which single claim would you verify first, and why?
- Which claim in this article is most likely to be revised as the sources update? How would you check its current status?
- If two sources disagreed about one of these facts, what would you need in order to trust one over the other?
Bibliography
No sources recorded.
Key claims and bibliography are generated from the same tracked claims and sources as the article page.