RT 4.0.15 Released

RT 4.0.15 is now available.

This release fixes an important regression in the ugprade scripts included in 4.0.14. If you attempted to upgrade from 3.8 with the RT FAQ Manager tables (FM_*) in your database, one of the upgrade scripts would error out.

If you were planning to upgrade from 3.8 using 4.0.14, please use 4.0.15 instead. If you have already upgraded to 4.0.14, there is no functional change in 4.0.15.

A permanent changelog is available.

RT 4.0.14 Released

I'm happy to pleased that RT 4.0.14 is now available.

This release is primarily a bugfix release. It also contains automated tests for security vulnerabilities announced earlier

A complete changelog is available.

RTIR Release Scheduling

As the next major version of RT for Incident Response (RTIR) is in final testing before release, we wanted to document our plans for the current RTIR release series.

RTIR 3.0 will join RT 4.0 as our stable series and will receive regular bugfix releases. All new development will be centered on RTIR 3.2 which will be compatible with RT 4.2 (the current RT development series).

Once RT 4.2 and RTIR 3.2 are released, we expect that RTIR 2.4 and 2.6 will follow the same end-of-life schedule as RT 3.8 and the RT FAQ Manager announced here.

At this time, RTIR 2.4 and 2.6 are only receiving security or critical bugfixes, such as these patches.

If you would like to help test the next RTIR release, the third release candidate is available.

RT 4.0.11 Released

I'm happy to announce that RT 4.0.11, the latest stable release, is now available.

This release of RT contains two large updates.

The WYSIWYG editor (CKEditor) used on ticket creation and reply pages has been updated to address numerous reports of breakages when using IE 10. It also includes fixes for many other browsers. You can read more about the included changes. We are shipping 3.6.6.1, upgraded from 3.4.1.

If you use RT with mod_perl and have not updated from SetHandler perl-script to SetHandler modperl, RT will now refuse to start. You can read more about mod_perl configuration here.

A complete changelog is available

RT 3.8.16 Released

I'm happy to announce that RT 3.8.16, the latest maintenance release, is now available.

Recent support for partitioned GnuPG emails introduced a deadlock situation for large QP/Base64 emails with GnuPG enabled. In addition, this release resolves a number of issues running the test suite on newer versions of perl.

RT 4.0.10 Released

I'm happy to announce that RT 4.0.10 is now available.

This release contains several bugfixes and a fix for a regression introduced in 4.0.9. If you have a Queue configured so that users have SeeQueue and CreateTicket but not ShowTicket (they can create tickets, but won't be able to see them after creation) then any Custom Fields assigned to that Queue and filled in during creation would be lost during submission.

A complete changelog is available.

RT 4.0.9 Released

I'm happy to announce that RT 4.0.9 is now available.

This release contains a number of bugfixes since the 4.0.8 release. It also contains the first set of embargoed security tests fixed by patches released on 2012-05-22. These are the tests for vulnerabilities fixed in RT 4.0.6 and RT 3.8.12.

This release also requires a newer HTML::RewriteAttributes. You will be prompted to upgrade when upgrading RT or when manually running 'make test-dependencies'.

If you have set a custom @JSFiles in RT_SiteConfig.pm, you will need to amend this to include the new jquery.cookie.js file added to RT_Config.pm. See UPGRADING-4.0 for more details.

A complete changelog is available.

Release Scheduling

We're currently hard at work on the next major version of Request Tracker (RT 4.2) and we want to share our plans for the current RT release series.

As our current stable release, RT 4.0 will continue to receive regular bugfix releases. All new features are targeted for 4.2. This allows us to provide a consistent and stable upgrade path within the 4.0 series.

At this time, RT 3.8 will only be receiving security or critical bugfixes. When we release 4.2, we will announce an end of life schedule for 3.8.

The RT FAQ Manager was integrated into RT 4.0 as the Articles feature. Once RT 3.8 is no longer supported, support will also cease for RTFM.

With the release of 4.2, we also plan to stop fixing bugs for certain old and outdated web browsers. In particular this means IE6, but may also include other browsers that cause us maintenance problems. We will not actively break compatibility with these browsers, but we will not be developing patches to fix them.

RT 4.0.7 Released

I'm happy to announce that RT 4.0.7 is now available.

This release contains a number of bugfixes since the 4.0.6 release. In particular, we have adjusted the CSRF warning for a few pages based on user feedback.

This release bumps dependencies on Email::Address, FCGI and IPC::Run so please make sure to run 'make testdeps' and if required 'make fixdeps' before upgrading. Running 'make upgrade' will also check your installed versions for errors.

Security

• Bump the FCGI dependency to one which closes CVE-2011-2766 The 4.0 series did not specify a minimum FCGI version and it's possible that a vulnerable release of the perl FCGI module was installed when you set up an earlier release of 4.0.x

Features

• Allow specification of your CSRF Whitelist Referrer using *.example.com
• Allow searching for tickets associated with articles using a:42
• Upgrade our Date/Time picker JS, allow unsetting of CFs
• Improve display of circularly linked tickets
• Optimize the large table changes between 3.2 and 3.4 for MySQL
• Provide a better error if your CreateTickets template is malformed
• Add the ExtractTicketId function to make customizing ticket id matching easier

Bugfixes

• Don't trust emails that claim to be UTF-8, convert it to UTF-8 before storing
• Fix a shredder bug when deleting a user and replacing it with another user
• Remove CSRF restrictions on search results page
• Ensure that TransactionBatch scrips always run in the RT::System context rather than having some sub-objects in the original user's context.
• Better display of multipart/related mail
• Remove some warnings when running under Perl 5.16
• Better errors when viewing approvals without rights
• Bring back rounded corners on FireFox >= 13 by using the standard border-radius property
• $Users->LimitCustomField now ignores disabled ObjectCustomFieldValues properly (same for other non-ticket objects).
• Versions of IPC::Run < 0.90 could truncate labels on charts that contain UTF-8 characters
• Fix a rendering issue where certain emails would cause the history to render progressively more staggered to the right
• Make owner:falcone and owner:falcone@example.com work
• CF.{Foo} TicketSQL searches are now case insensitive on Pg and Oracle
• Tickets with Unicode subjects created through the Web UI could end up being corrupted on reply because of other headers passed to MIME::Head
• Ignore DECRYPTION_INFO from GnuPG 1.4.12
• Record LastUpdated(By) on Scrips
• Simple Search now handles Custom Fields with dashes
• Remove another hardcoded use of 'resolved' in the mailgate unsafe actions
• When deleting dashboards, also delete subscriptions
• Fix rendering of links from bin/rt
• Don't allow ticket creation if your REST form contains an unknown field
• Skip users with empty email addresses in autocompletion
• Loosen our detection of mobile browser to search for the word 'mobile'
• Don't provide a charset on download of binary attachments
• Fix UseSideBySideLayout to not be cached across users
• Ensure that article searches are case insensitive
• QueueSummaryByStatus now uses the improved code from QueueSummaryByLifecylcle

A complete changelog is available from git by running

git log rt-4.0.6..rt-4.0.7

or visiting

https://github.com/bestpractical/rt/compare/rt-4.0.6...rt-4.0.7

although they will not load all of the commits.

RT 3.8.14 Released

I'm happy to announce that RT 3.8.14 is now available.

This release contains two fixes related to the 3.8.12 security release.

Access to search results URLs is now CSRF whitelisted, based on user feedback. An error in rt-email-dashboards has been corrected.

A complete changelog is available from git by running:

git log rt-3.8.13..rt-3.8.14

or on github with

https://github.com/bestpractical/rt/compare/rt-3.8.13...rt-3.8.14