RT 2.1.80 is now up for download. It contains a number of fixes since
2.1.78 and a couple minor enhancements. It’s my intent that 2.1.80 will
be announced as Beta 3, unless scrips are still broken. I expect that
Beta 3 will be the last beta release before RT 3.0.0. (We’ll have a
couple of release candidates before 3.0 feels just right, I suspect).
Jesse
Changelog:
257 237 Adding in a hook for clicky stuff in Message display; fixing
some minor issues with message parsing
258 238 logging cleanups. RT should now log with a service name, patch
from robrt for tickets_sql exception handling for 2186; group
admin menu hilgihting fix for 2052; graphvis RQL parser from
2123; fixing a bug in scripaction_overlay's Load routine;
fixed a bug that prevented some custom field searching
259 239 Bumping to 2.1.79
260 240 approvals cleanups; CustomField link cleanup
261 241 loc bug for Relationship listing
262 242 custom field value editing cleanups
263 243 fixing a bug that set 'Closed' dates for all new tickets
264 244 Looking into scrips misfiring
265 245 Adding back txn content to messages being sent
266 246 Txn notification header updates
267 247 UTF8 escaping bug fixes
268 248 Cosmetic cleanup for message content display ; installation
cleanups and fixes; Bumped to 2.1.80
Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.
RT 2.1.80 is now up for download. It contains a number of fixes since
2.1.78 and a couple minor enhancements. It’s my intent that 2.1.80 will
be announced as Beta 3, unless scrips are still broken. I expect that
Beta 3 will be the last beta release before RT 3.0.0. (We’ll have a
couple of release candidates before 3.0 feels just right, I suspect).
In the tickets search interface, “next page” doesn’t work, ie: the page
comes empty.
postgres.log has this error: LIMIT #,# syntax not supported
THERAMENE: Dangereuse mar�tre, � peine elle vous vit
Que votre exil d’abord signala son cr�dit.
(Ph�dre, J-B Racine, acte 1, sc�ne 1)
RT 2.1.80 is now up for download. It contains a number of fixes since
2.1.78 and a couple minor enhancements. It’s my intent that 2.1.80 will
be announced as Beta 3, unless scrips are still broken. I expect that
Beta 3 will be the last beta release before RT 3.0.0. (We’ll have a
couple of release candidates before 3.0 feels just right, I suspect).
A couple things:
noted. will be fixed in 2.1.81
Even though they don’t have AdminCustomField they can create a
custom field in any queue (yet they can’t disable it), is that
normal?
Create a custom field or add a custom field value to a ticket?
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
Both of these have been found and fixed. They should be out in 2.1.81On Thu, Mar 06, 2003 at 03:42:15PM +0100, Louis-David Mitterrand wrote:
On Thu, Mar 06, 2003 at 02:36:36AM -0500, Jesse Vincent wrote:
RT 2.1.80 is now up for download. It contains a number of fixes since
2.1.78 and a couple minor enhancements. It’s my intent that 2.1.80 will
be announced as Beta 3, unless scrips are still broken. I expect that
Beta 3 will be the last beta release before RT 3.0.0. (We’ll have a
couple of release candidates before 3.0 feels just right, I suspect).
A couple things:
-
e-mail submission is broken again:
RT::CurrentUser::CanonicalizeEmailAddress Unimplemented in RT::Interface::Email
-
here are the rights I have given are to the priviledged users
group:
CommentOnTicket
CreateTicket
ModifyTicket
OwnTicket
ReplyToTicket
SeeQueue
ShowTicket
ShowTicketComments
Watch
WatchAsAdminCc
ModifySelf
Even though they don’t have AdminCustomField they can create a
custom field in any queue (yet they can’t disable it), is that
normal?
–
PHEDRE: Malheureuse, quel nom est sorti de ta bouche ?
OENONE: H� bien ! votre col�re �clate avec raison :
J’aime � vous voir fr�mir � ce funeste nom.
(Ph�dre, J-B Racine, acte 1, sc�ne 3)
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.