Log message:
Update to 4.2.1
Changelog:
4.2.1:
This release is primarily a bugfix release; notable changes include:
Oracle:
* Resolve numerous issues with the 4.0 -> 4.2 upgrade steps on Oracle
* In-database sessions on Oracle are no longer truncated at 8k,
leading to spurious logouts
Internet Explorer:
* Fix submission issues under Internet Explorer
Rich text editor:
* If returning to a reply/correspond page with the back button, the
rich text editor will no longer double-escape previously written
content.
REST:
* Fix an empty 'text/plain' part when tickets are created using the
REST interface.
Other bugfixes:
* Optimize transaction display code to speed up long ticket displays
by short-circuiting transaction custom field checking.
* Supply a default $PATH for SMIME and GnuPG under FastCGI
* Support index upgrade steps on Pg when in a custom schema
* Close a memory leak in ColumnMap
* Fix "check all" checkboxes for new jQuery version
* Secondarily sort user ticket lists by id, as well as priority.
* Remove call to deprecated function used by PreviewScripMessages
* Many localization fixes (thanks to Emmanuel Lacour)
* Show customized rights in their correct tabs
* Ensure RFC2822 date format uses two-digit days in output
* Display iCal dates in the user's timezone, resolving off-by-one
errors for timezones significantly off from GMT.
* Correctly parse complex format strings for listing in the bottom of
the Query Builder
Callbacks:
* Move ModifyQueryProperties callback to before its values are used
* Additional callbacks on ticket modify pages
* Additional callbacks on ticket reply/comment page
* Additional callback on search results page
* Additional callback before transactions in history list
* Allow header callback to modify %ARGS
Features
* Allow bulk update to delete _all_ CF values for a given CF
* Support CF.Foo in columnmaps, in addition to CF.{Foo} and
__CF.{Foo}__
* Autocompletion CFs now autocomplete in search builder
* Support cascaded selects with any combination of listbox, dropdown,
and radio button
* Support ShowUnreadMessageNotifications in SelfService
4.2.0:
RT 4.2.0 -- 2013-10-03
----------------------
We're incredibly pleased to announce the availability of RT 4.2.0 - the
first release for the next major version of RT. This release adds
exciting new functionality, as well as streamlining and generalizing the
internals.
When upgrading, please be sure to review the upgrading documentation
available in docs/UPGRADING-4.2, as there are a number of
backward-incompatible changes that come along with the new version
number. Upgrading documentation is also available at
http://www.bestpractical.com/docs/rt/latest/UPGRADING-4.2.html
http://download.bestpractical.com/pub/rt/release/rt-4.2.0.tar.gz
http://download.bestpractical.com/pub/rt/release/rt-4.2.0.tar.gz.asc
a24bd767263cdcee92bf52c6b06a1a573aa0a615 rt-4.2.0.tar.gz
0717fd7d928efaadba2228de855c014e6be735cb rt-4.2.0.tar.gz.asc
A partial list of the new features in RT 4.2.0 is included below, and on
http://bestpractical.com/rt/whats-new/ Many of the new features will also
be described and demoed in a series of blog posts on
http://blog.bestpractical.com/ in the coming weeks.
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
contact@bestpractical.com.
- Alex Vandiver, for Best Practical
* Much improved reporting via search result charting
- Multiple group by and statistic calculations in a table
- Time statistics such as average, minimum, and maximum durations
between Created and Resolved, Created and Started, Started and
Resolved, and more.
- More robust layout of charts
* Increased performance for searches and ticket pages
- Faster searches on all databases (especially Pg)
- Ticket pages load quicker
- Menus load before the rest of the page is loaded
- History is loaded asynchronously
- Faster serving of static assets
* Scrips per queue
- Apply scrips globally or ad-hoc to individual queues, a la custom
fields
- Less duplication of scrips and/or need for empty templates
* Custom field groupings
- Display CFs in configurable groupings (boxes) on the ticket
display/edit pages
- Includes arbitrary grouping names as well as standard ticket
groupings (Basics, Dates, People, Links, etc.)
* User summary pages
- Display information about users such as tickets, history, groups,
etc.
- An extended "More about requestors" page for any user
- Easy to get to via links and user search
* HTML templates enabled by default for new installs, available for
upgrades too
* History improvements
- Rich text/HTML messages are preferred for display by default
- Images are inlined with text in ticket history display instead of
presented at bottom
- Clickable users, tickets, articles, and other items
* Many interface improvements, such as:
- Per-user preferences for the dashboards which appear in the Home
menu
- Floating page menu for quicker access to ticket actions, subpages,
etc.
- Autocomplete for ticket links, including when merging
- Autocomplete available to self service users
- Improved CF and links display in search results
- Sticky simple search for quick search refinements
- Attachments on reply can no longer be mixed up when replying to
multiple tickets at once
- ReassignTicket right to assign tickets without stealing first;
useful for managers
* S/MIME support integrated with GnuPG support
- Decrypt and verify incoming GPG and SMIME messages
- Send all outgoing messages as either GPG or SMIME
* Migration tools
- Migrate from one database type to another (MySQL, Pg, Oracle)
- Merge multiple RT instances together
* Thousands of bug fixes; nearly 2000 commits totalling more than
250,000 lines of code changed.
4.0.18:
This release is primarily a bugfix release; most notably, it addresses
compatibility issues with recent versions of the Encode perl module.
Notable changes include:
Email
* Cope with Encode version 2.33 and later, which altered their internal
functionality and caused RT to double-encode Subject lines in
outgoing email.
* Fix HTML rendering errors in dashboard emails.
* Fix overzealous quoting around decoded MIME words.
Administration
* In the rights UI, entering the name of a user or group which already
has rights will now correctly select them for rights granting, as if
their name had been selected.
* Display types in the "applies to" dropdown for custom fields in
consistent order
* Paginate the Queues list in the administrative interface into 50
results per page.
* Support for cascading selections with a multiple-select parent.
* Clarify that $ParseNewMessageForTicketCcs only applies to new, and
not existing, tickets.
* Clarify how an undefined $RTAddressRegexp is treated, and that it
does not come at any notable performance penalty.
Logging
* Fix verbosity of syslog messages; now only the 'debug' level includes
originating filename and line.
* Include process ID in log messages, for ease of isolation in a
multi-process environment.
* Log the From: address of incoming mail which triggered an error, for
ease of debugging.
Other Bugfixes
* Avoid linking trailing punctuation, or html tags, in URL anchors in
MakeClicky
* Fix the Quick Search (QueueSummary) portlet when non-lowercase statuses are used.
* Show Date and DateTime custom fields in the user's format and time
zone in search results.
* Allow rt-email-group-admin to be passed an email address that RT is
not already aware of.
* Show submitted content from the user on errors in REST submission,
for ease of re-editing and re-submission.
|
Log message:
Update to 4.0.17
Changelog:
RT 4.0.17 -- 2013-08-02
-----------------------
This release fixes an important regression in the upgrade script
included in 4.0.14, 4.0.15, and 4.0.16. Attempting to upgrade from 3.x
would skip key upgrade steps. New installs, and sites upgrading from
within the 4.0.x series, are unaffected.
RT 4.0.16 -- 2013-07-29
-----------------------
This release fixes an important regression in the Shredder tool included
in 4.0.14 and 4.0.15. Attempting to run the Shredder tool from the
command line would fail with a compile-time error.
4.0.15 Release Notes
2013-07-25
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.
4.0.14 Release Notes
2013-07-25
This release is primarily a bugfix release. It also contains automated
tests for security vulnerabilities announced on 2012-10-25.
Features
* Ticket watcher searches that involve a large number of ORs will now
use a much-improved SQL query, instead of the old many-join solution.
* Do a better job wrapping text before quoting it in a reply.
* Simple search now supports @example.com to search for tickets
requested by users with email addresses ending in @example.com.
* If our display parsing of an HTML attachment fails for known reasons,
a better error message is provided, directing admins to contact us with
a sample.
* Tickets created via the REST interface can provide attachments.
* Comments and Replies in the REST interface may include a Content-Type.
* RT's Quote recognition now triggers on > and ignores things like
!,|,#,% etc. This should resolve a number of false positives.
* RT is now compatible with perl 5.18.0.
Bugfixes
* Resolve several corner cases where RT's database handle can be
disconnected unexpectedly.
* When a TicketSQL query fails, report that failure to the user rather
than silently displaying an empty ticket list.
* Display and add attachments to tickets in alphabetical rather than
random order.
* Ensure that LifeCycle statuses are compared case-insensitively.
* Report Reminder creation/updates back to the user more consistently.
* Ensure that Reminders are created in the reminder_on_open LifeCycle
configuration.
* The Bookmarks portlet is no longer unlimited and obeys standard
homepage restrictions.
* Display non-ticket links in search result formats.
* RT::CurrentUser->Attributes now returns attributes for the relevant
User, resolves a bug noticed in RT-Extension-MergeUsers.
* Always filter empty OrderBy directives, which may come from old saved
search preferences.
* Uploaded attachments are now always marked Content-Disposition: attachment.
* Allow Custom Field Values to change case.
* The error message for Truncated Attachments is now marked text/plain
rather than plain/text.
* When bulk updating Tickets with Transaction Custom Fields, the
list of Transaction Custom Fields is based on the Queues of the
Tickets displayed, not the Queues of the Tickets updated in the
previous update.
Administration
* Clarify the cause of certain PostgreSQL full text indexing errors.
* Remove an error preventing logging of an actual error related to
problems storing sessions.
* Clean the lock files used for file based sessions more aggressively.
* SetOutgoingMailFrom will now accept an email address to be used
globally.
* OverrideOutgoingMailFrom now falls back to the global
CorrespondAddress if the Queue does not declare one.
* rt-setup-database now prints the DatabasePort when describing the
database it is modifying.
* rt-setup-database tries to detect when it is being run from an invalid
location or being given an invalid upgrade directory.
* rt-setup-database detects an upgrade running on Pg 9.2 and directs the
admin to install a newer DBD::Pg.
* rt-email-digest no longer prints output when sending digests unless
the --verbose flag is passed.
Developer
* CleanSlate on collections more thoroughly resets the collection.
* A new callback and better support for JS/CSS tweaking of our
Autocompleter display formats.
* New warning when an RT::URI::* resolver object cannot be created.
* Extensions may use rt-setup-database --action upgrade --package
extension to provide RT's friendlier upgrade infrastructure.
* Refactoring of TicketSQL parse to support TxnCF.{CFName} or
QueueCF.{CFName} in the future.
Documentation
* Correct the example backup `date` command in backups.pod
* MailCommand's testfile argument is now documented.
* Multiple cleanups to better support http://docs.bestpractical.com
* RT::Classes and RT::Principals now default to honoring the Disabled flag.
|