- 1 Nota Bene
- 2 Introduction
- 3 Help maintain this page
- 4 List
- 4.1 Asset Tracker
- 4.2 Branded Queues
- 4.3 Command by email
- 4.4 Conditional CustomFields
- 4.5 Export search results as XLS
- 4.6 External Authentication
- 4.7 Extract Custom Field Values
- 4.8 Group Summary
- 4.9 Mandatory Fields
- 4.10 Mandatory requestor
- 4.11 Mandatory subject
- 4.12 Notify users/groups
- 4.13 QuickCalls
- 4.14 Reference i-doit Objects
- 4.15 Richtext CustomField
- 4.16 Rights Matrix
- 4.17 Service Level Agreements (SLA)
- 4.18 Shredder
- 4.19 Stall Future Ticket
- 4.20 Toggle SuperUser right on/off with a link
- 4.21 User details
- 4.22 Watched queues
- 4.23 Workflow Builder
- 5 Other
- 6 Writing your own extensions
The Best Practical website now contains a list of standard and known-maintained extensions at http://bestpractical.com/rt/extensions.html. If you know of a maintained extension that doesn't show up there, send mail to webmaster at bestpractical.com.
Here is a list of RT extensions packaged and available from CPAN or other places.
Most of these extensions are prepared with Module::Install::RTx module, which allows you to package extension easily and quickly. People who would like to package their extensions should read the module's documentation.
Help maintain this page
Please sort and refactor this list; RT::Extension is a verbose but lexigraphically equivalent form of RTx. Also note, that links to a particular version of a module on search.cpan may rot when later versions are released, used a perldoc query instead.
Integrated into RT 3.8, read UPGRADING and etc/upgrade/3.8-branded-queues-extension.
RT 3.2-3.6: This extension allows sites to "Brand" individual queues with distinct tokens in the Subject headers of outgoing email messages.
Command by email
RT::Extension::CommandByMail allows you to change metadata of ticket via email:
- Supported commands
- Man page
- Installation instructions
- requires patching on RTs older than 3.6, but works out of the box on modern RT
- Authors: Best Practical
- See also: Extract Custom Field Values
- Tip: strip out commands from ticket and emails sent by RT
This RT Extension allows to display/edit a custom field conditioned by the value of another (select) custom field for the same object, which can be anything that can have custom fields (ticket, queue, user, group, article or asset). RT::Extension::ConditionalCustomFields
Export search results as XLS
This RT Extension allow users to download search results in Microsoft Excel binary format. This typically fix encoding problems for non-ascii chars with the standard TSV export included in RT. Extension root
Allows authentication from any LDAP or DBI-supported data source. Also allows the use of a browser cookie to implement Single Sign-On with other web code using a DBI authentication backend.
For RT-3.6.x (unsupported)
Extract Custom Field Values
Allows to extract CF values from email headers or body.
This RT Extension allows RT to display semantic information about any group, mainly through CustomFields attached to this group.
It displays information about a group on a Group Summary page, similar to what is done about a user. A Group Summary page includes the name, the description and CustomFields of a group. The Group Summary page can be accessed from any tabs of Admin/Groups and is linked to any display of a principal which is a group (just like any display of a principal which is a user is linked to the related User Summary page).
This module also provides a Group Summary Search feature and links results to related Group Summary pages.
This RT Extension enforces users to fill standard fields defined in RT site configuration file when creating a ticket via the web interface. RT::Extension::MandatoryFields
This RT Extension enforces users to fill the requestor when creating a ticket via the web interface. Extension root
This RT Extension enforces users to fill the subject when creating a ticket via the web interface. Extension root
Part of RT 3.8
Helps setup and manage scrip actions that allow you to notify particular groups of users.
See also EmailGroup
Reference i-doit Objects
This extension gives you the opportunity to combine an issue tracker like RT with an IT documentation tool / CMDB like i-doit. It uses i-doit's API to relate a ticket with one or more CIs / objects managed by i-doit. On i-doit's side you are able to view all tickets related to an object. This extension also supports i-doit's multi-mandator functionality.
This RT Extension provides a new type of custom field, similar to Text but with wysiwyg editor when editing value. RT::Extension::RichtextCustomField
- Extension root == RSS Feeds ==
Add arbitrary RSS feeds to your dashboards
Service Level Agreements (SLA)
This RT Extension enables the specification and usage of SLA's (Service Level Agreements).
- Version 0.01_01 is the latest that supports RT-3.0.x
- RT 3.2.x is unsupported
- Versions >= 0.02 works with RT 3.4.x and greater, 3.4.1 requires patching
- Included in 3.8.x
Stall Future Ticket
This RT Extension allows to automatically stall created tickets with a start time in the future. RT::Extension::StallFutureTicket
This RT Extension allow users with SuperUser right to quickly enable/disable this right with a simple link at the top of each page. This way, they can work like standard users for day to day usage and enable SuperUser right only when needed. Extension root
This RT Extension allows to quickly display watchers personal details on a ticket. Extension root
This RT Extension allow to display the list of queues the user is watcher, in the user configuration tab. Extension root
This RT Extension is useful for creating Approvals and Workflows.
RTx::WorkflowBuilder by Chia-liang Kao
- Works in 3.8 with a tweak to /path/to/rt/share/html/Callbacks/Timeline/Ticket/Elements/Tabs/Default to change the tab index from 'j' to something else e.g; 't'. Otherwise, the Bulk Update tab is clobbered.
Writing your own extensions
- Homepage Components (Portlets): WritingPortlets