Election Protection Runs on RT

Election Protection Runs on RT

The national, nonpartisan Election Protection coalition works to ensure that all U.S. voters have an equal opportunity to participate in the political process. On election days, they provide resources for voters across the country to protect the right to vote and Request Tracker is the engine that manages all of those requests. Read on to learn more about how RT supports this important project.

Share this post:

Running RT with Docker

Running RT with Docker

Docker provides a great environment for quickly spinning up Linux working environments. At Best Practical we use Docker to test RT using many different options and configurations.

Share this post:

Managing Service Level Agreements (SLAs) in RT

Managing Service Level Agreements (SLAs) in RT

Service level agreements (SLAs) are an important aspect of support agreements. If your organization provides support, it's important to track requests and make sure the team knows when they need to respond. RT's SLA features automate this tracking so you can be sure your support team responds on time.

Share this post:

Announcing Our First 2017 Request Tracker Training!

Announcing Our First 2017 Request Tracker Training!

Paris Request Tracker Training, April 24 - 26, 2017!

Share this post:

Request Tracker Training in LA!

Request Tracker Training in LA!

New dates for the Request Tracker training in LA!

Share this post:

RT 4.0 Reaches End of Life

RT 4.0 will reach end of life on February 15, 2017. It is recommended that users upgrade their RT instances to a supported version, 4.2 or 4.4, before that time.

Share this post:

RT/RTIR Training Update

RT/RTIR Training Update

We're moving the LA training and announcing Boston training dates!

Share this post:

RT: The Cure for the Shared Inbox

Request Tracker, with its first class support for email, offers the familiarity of a shared inbox. On top of that, RT brings the organizational power of an enterprise ticketing system.

Share this post:

September! Join us for RT Training in LA, Now With More Workshop!

September! Join us for RT Training in LA, Now With More Workshop!

We're coming to LA with our new 3 day RT training!

Share this post:

RT 4.4.1 released

We're pleased to announce the availability of RT 4.4.1. This release addresses several bugs in RT 4.4.0 and also adds a few small but important features. The list of new features is provided below. Please see our official release announcement for more information, including the complete set of changes and bugfixes.

Download RT today!

  • Administrators and users can now choose to place signatures above the quoted message in replies (RT_Config setting SignatureAboveQuote and the similarly named user preference). This also improves the specific spacing between quotes and signatures in all configurations.
  • Users may now choose to suppress dashboard email when all of its searches have no results. This is controlled by the new "Suppress if empty" checkbox on the subscription page.
  • The Dashboard subscription recipient options have been greatly expanded from a single text field (which happened to support multiple email address separated with a comma) to a robust user/group search.
  • Users may now select a specific language for each dashboard email subscription. Administrators can customize the method by which dashboard email language is chosen (including specifying an ultimate fallback other than English) with the EmailDashboardLanguageOrder RT_Config setting.
  • The "hide unset fields" preference now also hides unset custom fields, obsoleting RT::Extension::CustomField::HideEmptyValues.  Additionally there is now a toggle button at the top right of the ticket display page for quickly toggling whether unset fields are hidden or shown.
  • There is a new SetInitialCustomField right that permits setting custom field values on records (tickets, assets, articles) while you are creating them. It does not permit modifying custom field values of existing records. Users with SetInitialCustomField but without ShowCustomField will still be able to specify a custom field value at create time but not see it afterwards.
  • Administrators and users can now choose to display queue dropdowns as an autocomplete field (RT_Config setting "AutocompleteQueues"), much like is available for Owners. If your RT instance has many queues this option improves performance and usability.
  • New config for hiding time worked, time estimated, and time left from unprivileged users in the self-service interface (RT_Config setting "HideTimeFieldsFromUnprivilegedUsers"). This also adds a hook point RT::Ticket::CurrentUserCanSeeTime for further customization.
  • Long attachment lists can now be truncated to show only the X newest attachments, with an AJAX "Show all" link, (RT_Config setting "AttachmentListCount"). This should improve the performance and usability of both ticket display and ticket reply pages.

Share this post: