Features:
New config option 'OldestTransactionsFirst'.
By default, RT shows newest transactions at the bottom
of the ticket history page, if you want see them
at the top set this to 0.
Email plugin may return special constant to indicate
that it's done requested action and RT shouldn't
run default action handling code.
See also RT::Interface::Email.
Added support for timezones in RT::Date::SetToMidnight
method, this allowed us to fix problems with searches
by date.
Applied David Schweikert's patch that adds the useful
LastUpdated field to the fields returned through
the REST interface.
Added a "RH" RedHat layout option to config.layout.
Thanks to Paulo Matos.
New command line options in the rt-crontool script:
* add --transaction argument with two possible
values: 'first' and 'last'
* add --transaction-type argument to allow a user
to select type of transaction, for example
'Correspond' or 'Comment'.
With these changes crontool can send notifications
and other actions which need access to transaction
object.
New callbacks in html/Ticket/Elements/ShowSummary:
LeftColumn and RightColumn.
Display a custom field value without lists HTML markup
when a ticket has only one value for the custom field.
Add additional HTML classes to the cells in
Ticket/Elements/ShowBasics and Ticket/Elements/ShowDates
mason templates.
Fixes:
Don't die any more on error during custom fields
creation in rt-setup-database, but report and
continue with next object.
Dropped 'exit' call in exceptions handling code.
Fixed untake operation during tickets transfer
between queues when an owner has no right to own
the ticket in the destination queue and the
current user is different person. Note in new
implementation we write untake tansaction from
RT_System user.
Fixed problem when RT were failing with error:
"Couldn't call method IsLocal on undefined value".
Got rid of some noisy warnings and cleaned up
some code.
Fixed attchments loosing during next steps:
1) open ticket #1
2) click reply
3) upload attachment
4) open ticket #2 in another browser window
5) send reply to the ticket #1
RT was loosing uploaded attachment due to step 4) as RT.
Finding disabled groups should actually find them, now.
Fixed `rt ls -l` when RT server isn't at /.
Thanks to Mark Eichin.
Reed Loden caught a perltidy error that, somewhat
terrifiyingly, was still a valid mason page.
People may saw error "Could not convert attachment
from assumed utf8 to ''" in the log. We don't even
try to convert any more when target encoding is empty.
Fixed maxsize attribute of input fields for subject.
In DB we have limit 200, but these tags were set to
old value of 100.
Backported fix for TimeTaken updates. RT could call
method _UpdateTimeTaken on record objects that have
no such method.
Fixed RT failures under mod_perl2 with Oracle database.
In QuickCreate element now we use SelectNewTicketQueue
instead of SelectQueue.
Fixed problems on server start up with error message
'Not root path(s) specified'.
Now we load only required regular expressions from
Regexp::Common namespace.
In RT::Tickets::_EnumLimit now we load referenced object
only if value is defined and is not number, this avoid
several fetches from caches or in worst case from DB.
Use this advantage in Quicksearch element, change in
"RT at glance" load time should be noticable on systems
with many queues.
Added handling for all possible errors in
the RT::Action::SendEmail module.
Improved handling of errors in the RT::Template class.
In the RT::Group method 'crit' was being called on
the wrong object. Thanks to Todd Chapman
Allow an administrator to add 0(zero) as a custom field
value.
Fixed decoding of MIME headers, this chould should fix:
* problems with non-ascii names of attachments
* problems with partly encoded fields with '=' chars
in not encoded parts, for example:
X-MyHeader: key="plain"; key="=?encoded?="
X-MyHeader: key="=?encoded?="; key="plain"
Fixed RT::Transaction::OldValue and ::NewValue in situations
when values of {Old,New}Reference fileds are false. You may
saw effect of this bug in a ticket's history saying that
custom field value was changed from "random" value to the
XXX instead of expected "custom field was set to XXX value".
Todd Chapman discovered a case where RT's mail gateway would
default to the RT::SystemUser if no valid 'From' header were
found. This could allow a malicious user to create tickets or
reply to tickets, but not to gain access to data.
Localization:
Updated German translation. Thanks to Torsten Brumm.
the owner of all installed files is a non-root user. This change
affects most packages that require special users or groups by making
them use the specified unprivileged user and group instead.
(1) Add two new variables PKG_GROUPS_VARS and PKG_USERS_VARS to
unprivileged.mk. These two variables are lists of other bmake
variables that define package-specific users and groups. Packages
that have user-settable variables for users and groups, e.g. apache
and APACHE_{USER,GROUP}, courier-mta and COURIER_{USER,GROUP},
etc., should list these variables in PKG_USERS_VARS and PKG_GROUPS_VARS
so that unprivileged.mk can know to set them to ${UNPRIVILEGED_USER}
and ${UNPRIVILEGED_GROUP}.
(2) Modify packages to use PKG_GROUPS_VARS and PKG_USERS_VARS.
changes are apparently minor to a end user (but not for the site
administrator).
It'd very hard and very long to provide a full list of changes. The main
changes in RT 3.4 are a complete rework of how Custom Fields are handled,
which means there is a lot more flexibility in that area now (including
Custom Fields for users, per-queue, per-transaction). RT 3.4 is also
supposed to be faster, which certainly is no bad news.
Another bonus of RT 3.4 are the availability of extensions, and I will
commit RTx::Shredder and RTx::RightsMatrix very soon.
Updating RT is not an easy task, be sure to backup your database, and don't
forget to grant the new rights to relevant people.
In pkgsrc, rt3 is also seeing a few changes. The main one is the situation
of the "local" path, which is now set to /var/rt3, which seems less lame to
me than the previous value. It could be debated, though.
INSTALL/DEINSTALL script creation within pkgsrc.
If an INSTALL or DEINSTALL script is found in the package directory,
it is automatically used as a template for the pkginstall-generated
scripts. If instead, they should be used simply as the full scripts,
then the package Makefile should set INSTALL_SRC or DEINSTALL_SRC
explicitly, e.g.:
INSTALL_SRC= ${PKGDIR}/INSTALL
DEINSTALL_SRC= # emtpy
As part of the restructuring of the pkginstall framework internals,
we now *always* generate temporary INSTALL or DEINSTALL scripts. By
comparing these temporary scripts with minimal INSTALL/DEINSTALL
scripts formed from only the base templates, we determine whether or
not the INSTALL/DEINSTALL scripts are actually needed by the package
(see the generate-install-scripts target in bsd.pkginstall.mk).
In addition, more variables in the framework have been made private.
The *_EXTRA_TMPL variables have been renamed to *_TEMPLATE, which are
more sensible names given the very few exported variables in this
framework. The only public variables relating to the templates are:
INSTALL_SRC INSTALL_TEMPLATE
DEINSTALL_SRC DEINSTALL_TEMPLATE
HEADER_TEMPLATE
The packages in pkgsrc have been modified to reflect the changes in
the pkginstall framework.
change (it breaks for callbacks).
Inspired from the commit to solve the same issue on the 3.4 branch of RT.
Bump PKGREVISION and Mason version requirement.
packages.
o Drop the frontend- and backend- options names and replace them with
simpler ones, now that we have the PKG_OPTIONS_GROUP mechanism it's
much more easier.
o Brick me for not having done that earlier.
o Really enforce the conflicts between backend-* and frontend-* options,
as the recent changes in the options framework might confuse people in
that respect. You know have to explicitly remove the suggested options
in your PKG_OPTIONS.rt variable.
as a separate package.
The change log for that versions is as always with RT very long and
verbose. However, it is only a bug-fix release, and quite a few of them
are fixed. Among other things, a Polish translation has been added.
See the detailed information in the Changelog file at the root of the
archive.
into the bsd.options.mk framework. Instead of appending to
${PKG_OPTIONS_VAR}, it appends to PKG_DEFAULT_OPTIONS. This causes
the default options to be the union of PKG_DEFAULT_OPTIONS and any
old USE_* and FOO_USE_* settings.
This fixes PR pkg/26590.
Collection.
This package is based on the work of Dieter Roelants in pkgsrc-wip, with
a lot of changes to make it proper WRT pkgsrc.
RT is an industrial-grade ticketing system. It lets a group of
people intelligently and efficiently manage requests submitted by
a community of users. RT is used by systems administrators, customer
support staffs, NOCs, developers and even marketing departments at
over a thousand sites around the world.
