RT 4.4.2 release candidate 1

We’re pleased to announce the availability of the first release candidate for RT 4.4.2. This release addresses many issues and adds several minor new features, listed below. A complete list of improvements is available at https://docs.bestpractical.com/release-notes/rt/4.4.2rc1.

We have redesigned how time worked is calculated per user and for children tickets. As always please be sure to review the UPGRADING-4.4 document at https://docs.bestpractical.com/rt/4.4.2/UPGRADING-4.4.html#UPGRADING-FROM-4.4.1-AND-EARLIER.


SHA-256 sums

08b35701234bba170e24114fed8488f47ac723f44e1f161c12483c40607453c3  rt-4.4.2rc1.tar.gz
ca5fd5c069dae9f205824f0321726272b69b5d9844b7597005db871912a59db1  rt-4.4.2rc1.tar.gz.asc

Shawn M Moore, for Best Practical

New features:

  • Custom fields now have a “New values must be unique” option.

  • Custom fields now support value canonicalization (for example,
    automatically changing input values to be all uppercase). See the
    @CustomFieldValuesCanonicalizers config option.

  • Ticket timers provide a comment box for quickly adding ticket comments
    to describe your time worked.

  • You can now set up default values for assets on a catalog level.

  • You can choose to display result counts on ticket search portlets using
    the new $ShowSearchResultCount config setting.

  • There is now a “Load all history” link for the “as you scroll” history
    loading mode, to allow you to use browser-based text search.

  • We now display a list of recently-viewed tickets in the
    Search -> Tickets -> Recently Viewed menu.

  • We have made RT::Extension::AdminConditionsAndActions part of core
    RT, so you can now easily configure the conditions and actions of
    your scrips right within the admin UI.