News and Views from the Makers of Request Tracker
RT 4.0.3 contained a serious bug wherein upgrades from any version ofRT 3 to RT 4.0.3 broke template interpolation; please do not use it. If you had previously upgraded from RT 3 to RT 4.0.0, 4.0.1, or 4.0.2, before upgrading to RT 4.0.3, you are not affected by this bug.
If you are currently running RT 4.0.3 and are affected by this issue, upgrading to RT 4.0.4 will resolve it.
I'm happy to announce that RT 4.0.3 is now available.
This release contains a number of bugfixes and small improvements since the 4.0.2 release; a few of the more notable ones include:
Due to a change in RT 3.8.9, which also affected RT 4.0.0 and higher, TransactionBatch scrips were run twice; this has now been fixed.
A new toggle has been added to expand all quote folding in a ticket's transaction history.
New "On Forward", "On Forward Transaction" and "On Forward Ticket" conditions have been added.
Ticket searches no longer forget which saved search they were loaded from when being updated.
A new "make jsmin" target has been added to aid in downloading, compiling, and installing jsmin.
Improved threading for automatically generated emails concerning a ticket.
Improved detection of Outlook-style message fowarding headers.
No longer error when a user has supplied a non-existant RT style; instead, fall back to the default. This is particularly relevant for users coming RT 3.8 with the 3.6 stylesheet applied, which no longer exists in 4.0.
Improved handling of files named "0", and Unicode filenames, in file uploads.
Tickets can no longer be linked to deleted tickets.
Restore missing menus on simple search result pages.
Fix support for perl 5.12 and later by removing a deprecated use of "defined %hash".
I'm happy to announce that RT 3.8.11 is now available.
This release contains a number of bugfixes and a minor security update in one of our dependencies:
Adjust FCGI dependency to one which resolves FCGI's CVE-2011-2766
New WebHttpOnlyCookies option, enabled by default, which hides RT's cookie from direct Javascript access.
Compatibility with perl 5.12 and 5.14, by removing deprecated "for qw(...)" and "defined %hash" syntax.
MySQL 5.5 compatibility, by specifying ENGINE=InnoDB rather than TYPE=InnoDB
Ensure that RT::Interface::Web's _Overlay, _Local, and _Vendor files are loaded correctly.
Fix session cleaner for on-disk sessions, broken since 3.8.0.
Ensure that only one "Based on" attribute is stored for each custom field.
Fix the loading of Shredder plugins, broken in 3.8.10.
I'm happy to announce that RT 4.0.2 is now available.
Continuing with our goal of faster release cycles and smaller changes between releases in a stable series, this release primarily contains fixes for a number of minor bugs. It also includes documentation updates and removal of an inefficient javascript minification option. Notable changes include:
Ability to reference global CFs by Name in RT::Action::CreateTickets
Installation of the docs/ directory into /opt/rt4/docs
Removal of the incomplete --binary flag option for the full-text search indexer
Fixes for a regression that caused group dashboards to vanish after creation and not appear in the list of dashboards
Rewritten forward functionality to generate mail that better represents the original messages received by RT
Removal of the pure Perl Javascript::Minifier module which slowed down
the first request to new webserver children. jsmin or another
external minifier is now required to minify RT's javascript. Refer to
the section about $JSMinPath in perldoc /opt/rt4/etc/RT_Config.pm
for how to configure jsmin.
I'm happy to announce that RT 4.0.1 is now available.
This release is a bugfix release. It contains a number of notable fixes identified since the 4.0.0 release:
Fixes for MySQL+Sphinx and native PostgreSQL full text search, and improved documentation.
Javascript to forbid running RT in a frame, to prevent clickjacking attacks.
Better detection and hinting of common web path misconfigurations.
Minified javascript with an external jsmin now works in fastcgi and mod_perl deployments. This requires that mod_perl deployments switch to 'SetHandler modperl'; see docs/web_deployment.pod .
Javascript fixes for IE8 in the admin UI.
Multiple warning fixes during the upgrade process.
Removed previously missed rights related to right delegation.
Best Practical Solutions provides unparalleled instruction in how to get the most out of RT.
2011 will bring two-day training sessions to six cities across the world. As we like to keep class sizes relatively intimate, register soon or we may not be able to guarantee you a seat.
These sessions will be offered in:
If you can't make it to these cities, please drop us a line to request a public training for your area in 2012.
This training will introduce you to the new features in RT4 as part of a comprehensive overview of RT. Whether you're an old hand at RT or a recent convert, you'll have a good understanding of all of RT's features and functionality by the end of the session.
The first day starts off with a tour of RT's web interface and continues with a detailed exploration and explanation of RT's functionality, workflows and configurability. We'll touch on basic administration, but concentrate largely on helping you and your team get the most out of your RT instance.
The second day of training picks up with RT administration and dives into what you need to safely customize and extend RT. We'll cover point-and-click configuration, upgrading and installing RT, development best practices, RT's API, building an extension, and database tuning.
It goes without saying that you'll get the most out of training if you attend both days of the course, but we've designed the material so that you can step out after the first day with a dramatically improved understanding of how to use RT or show up on the second day and get quickly up to speed on how to make RT do your bidding.
Learn more on our website: http://bestpractical.com/services/training.html
On Friday September 30th, 2011 Best Practical Solutions will cease support for the 3.6 series of Request Tracker. 3.6.0 was released on June 15th 2006 and the series has received only critical bug and security fixes since June 2008. We will continue to provide critical bug or security fixes until September 30th, 2011 if any are required.
We're currently developing a schedule for future RT series and will publish an end of life policy and schedule as soon as they are complete. The 3.8 series will continue to receive bugfixes at this time, but our development efforts will be concentrated on polishing RT 4.0 and working on the new features we have planned for 4.2.
We've released version 0.09 of RT-Authen-ExternalAuth. This is primarily a bugfix release. It ensures compatibility with all of the changes made in 3.8.10 and 4.0.0. If you've been having difficulty deploying RT-Authen-ExternalAuth or have been delaying an upgrade, please give it a test.
The extension is available from CPAN: http://search.cpan.org/dist/RT-Authen-ExternalAuth/
Today we're releasing RT 4.0.0. This release represents over a yearof hard work and more than 2000 commits. With a new major version number, we took this opportunity to tidy up some of the older bits of RT and allow us to grow features through the RT 4 series. We hope you'll find it a worthy successor to RT 3.
Many, but not all, of our new features are the result of work done for clients. Enhanced full-text search, the integration of RTFM as Articles, refreshed ticket create and update pages, better control of ticket notifications, Lifecycles, and quote-folding of emails in ticket display all began life as extensions we built for clients.
We've also heard your requests in the form of feature requests, bug reports and patches and they've driven our new theme for RT 4, a new logo and theme editor, new custom field types and display options, the mobile UI and reorganized and revised documentation. As a result of your feedback, we also fixed hundreds of bugs and improved performance.
With so many changes by 16 authors over the course of a year, it would be hard to summarize everything we added, fixed or improved. Over the next few weeks, we'll be posting a series of articles on what's new in RT 4.0 to this blog. A list of new features in RT 4.0 is also available at bestpractical.com/rt/whats-new-in-4.html.
If you'd like to explore all of the changes we've made in the run up to 4.0.0, visit github.com/bestpractical/rt/.
Download
download.bestpractical.com/pub/rt/release/rt-4.0.0.tar.gz
download.bestpractical.com/pub/rt/release/rt-4.0.0.tar.gz.sig
SHA1 Sums
b2cf8d2ceb8bf97e5eeb08cb7d05760ca148df9f rt-4.0.0.tar.gz
5a6b04bf9bb6437b74138bc6ad7eabae39d36e6d rt-4.0.0.tar.gz.sig
We've done our best to ensure that upgrading from RT 3 to RT 4.0 will be as smooth as possible for you. If you have questions as you upgrade, please don't hesitate to write to rt-users@lists.bestpractical.com for community support. If you'd rather have professional support from the folks who built RT, drop us a line at sales@bestpractical.com.
We've talked our sales team into including free basic upgrades from RT 3 to RT 4 if you sign up for a new RT 4 support contract within the next two months. The new RT 4 support contracts are less expensive and come with lots of great new features.
In the process of preparing the release of RT 4.0.0, we performed an extensive security audit of RT's source code. During this audit, several vulnerabilities were found which affect earlier releases of RT.We are releasing versions 3.6.11, 3.8.10, and 4.0.0rc8 to resolve these vulnerabilities, as well as patches which apply atop 3.6.10 and all versions of RT 3.8.