On 17/06/2008, at 10:48 PM, Jason Fenner wrote:
It looks like you have two options:
1) You can add to your search/query a line that says 'Due 0'
What this will do is only return results that have a due date set,
it will not return results without a due date set.
You could then run a
On 18/06/2008, at 11:43 PM, David Nalley wrote:
Hey guys,
I am running a pilot installation of RT and experiencing some
performance anomalies
A bit about the environment:
RT 3.6.6 on CentOS 5, using mod_perl against Postgres 8.1. Postgres
and
RT on separate boxes, and are on the same
Dear all,
I installed a request tracker on a FreeBSD system. The request tracker is
working well but I have problem injecting my administative mails into it. When
i tried to send email into the request tracker, sendmail returns this error:
404 Not Found
I've had a read of the list archives, and a read of the Wiki, and just
wanted to check something before I suggest something as possible that my
team will hang me for :)
We have an operational instance of RT 3.6.5 with a rather unusual name.
We'd like to change the instance name to something more
Changing:
Set($rtname, 'new.name');
Set($EmailSubjectTagRegex, qr/(?:old\.name|new\.name)/i);
Should be all you have to do.
James Moseley
Graeme Fowler
My RT is installed and works except that when someone replies to a
ticket or updates the status and it is to supposed to email the
requester as well as other people in the group watching the queue.
However, it is not sending any of those emails. It also does not send
to anyone I manually put in
Thanks for the response, Kenn, but I don't think that describes
this particular problem. I'm concerned with the case where
you might like to have a ticket show up in two queues, and
updates be seen by the union of the watchers of those two
queues. For instance, we have queues for the windows