I've been getting this error too, but it occurs when I click Update
Ticket after composing a comment or reply for a ticket. What's
especially annoying is when I click Back, my comment/reply is no longer
in the WYSIWYG editor. But if I retype the message and click Update
Ticket again it goes
My rt.log file has the following error,
[Thu Jun 12 02:30:17 2008] [warning]: DBD::mysql::st execute failed: You
have an error in your SQL syntax; check the manual that corresponds to your
MySQL server version for the right syntax to use near 'AND ACL.PrincipalType
= Groups.Type AND
(follow-up)
fyi, I looked at the stack trace, and there is a
lib/RT/Interface/Email/Filter/TakeAction.pm module in the stack trace. This
module is not bundled with RT 3.6.6 so my problem may be there.
Jason
___
could use the Take right to determine which queues different groups should
see.
Jason
Jason Long [EMAIL PROTECTED] 9/21/07 8:43 AM
This patch changes the behavior of the newest unowned tickets list
to limit the query to queues where the user has the take right.
It's kind of a hack, since
[EMAIL PROTECTED] wrote:
Performing queries using 'Requestor = X OR Cc = X OR AdminCc =X' in 3.6.3
yielded very fast results - a few seconds. However, doing the same search
in 3.6.4 resulted in a timeout after four minutes.
Using 'Watcher = X' is the preferred solution, faster, etc (and what I
Drew Barnes [EMAIL PROTECTED] 3/27/07 9:32 AM
In other words, I want to assign someone rights to a ticket without
putting them on the notification list.
Make a Supervisor group with all appropriate rights?
That would give them rights to more than just that one ticket, wouldn't
it?
Jason
Tim Wilson wrote:
Hi all,
Anyone using LDAP Auth for RT with Novell eDirectory?
Yep.
I've been working through the LDAP documentation at the wiki
(http://wiki.bestpractical.com/index.cgi?LDAP) and I've got things
mostly working with RT 3.6.1 and Novell eDirectory 8.7.x. I can log in
to
Mathew Snyder wrote:
I've built a development server for the purpose of doing testing before
making changes to our production environment. Naturally, it has a URL
that differentiates it from our production server
(rt-devel.ourcompany.com vs. rt.ourcompany.com). However, in order to
further
