RT 6.0.0 Released

We are thrilled to announce the release of Request Tracker (RT) 6.0.0! This major release introduces an updated user interface, new customization features, integration of popular extensions into the core, and numerous enhancements to improve performance, usability, and administration.

You can see details and videos on our blog showing how RT looks with htmx and Bootstrap 5, along with new ticket and saved search features. And you can now customize your ticket and asset pages to contain only the elements you need, and you can position them however you want to.

You can get the new version here:

https://download.bestpractical.com/pub/rt/release/rt-6.0.0.tar.gz
https://download.bestpractical.com/pub/rt/release/rt-6.0.0.tar.gz.asc

SHA-256 sums

508f9a08f17b20ae8c96faf16da4a0b51e74a5332a69146ccfd3f4596eb5db2d  rt-6.0.0.tar.gz
0d3bc45d065bf633af4837ba9cc1562870860a8e561b4e30d1408b6c8bd2dd0a  rt-6.0.0.tar.gz.asc

This release also contains many other big new features including scrips support for assets and articles, full-text search enhancements, and accessibility improvements. The TimeTracking and ArticleTemplates extensions are now core in RT 6, and configuration for extensions is available in the RT System Configuration interface.

We have added Selenium to our automated test suite to help test htmx and you can see RT’s 45,000+ tests run automatically on GitHub every time we push and update and continue to work to improve RT.

A complete changelog is available from git by running:
git log rt-5.0.8…rt-6.0.0
or visiting Comparing rt-5.0.8...rt-6.0.0 · bestpractical/rt · GitHub

You can also find a comprehensive list of changes in 6.0.0 in our release notes.

We think you’ll enjoy the updates in RT 6 as much as we are! :rocket:

1 Like

I see that RT6 was released when will there be a RTIR version compatible with 6?

We’re working on RTIR right now and hope to have a new release soon.

Hi,
I just noticed a bug in RT6.0 when running behind a web proxy.
In the Header file rt/share/html/Elements/Header at a1b836790db27833cdd788ce34bc63b9eb672334 · bestpractical/rt · GitHub you always reference RT::Interface::Web::RequestENV(‘REQUEST_URI’) without respecting a subpath from the config ($WebPath). This leads to the start page not loading because the REQUEST_URI is always without the $WebPath part as fcgi-server runs on /. Overwriting the REQUEST_URI in the reverse proxy is also not working, as fcgi expects all paths at /

Indeed, you are correct. I created a ticket in our public RT to track this issue. Watch there for a possible patch before the next release. Thanks for the bug report!

Congratulations on this milestone.

How much RAM is a clean install expected to consume?
I installed this version and ran it using Apache+mod_perl, and it increased my system’s RAM utilization by almost 6GB.