On Wednesday 15 of January 2014, Kevin Falcone wrote:
> It will be re-queued and tried again
> when it fails to submit to RT, so it'll be somewhere in your queues
I find it to not always be true. For example when our mysql died then rt-
mailgate didn't return any error BUT rt itself created bounc
I just upgraded to RT 4.2.2 yesterday, and whenever a user merges a ticket, the
responsible apache processes maxes out memory usage on the system and the
system slows to a crawl until the OS kills the process, since the system is out
of memory.
Is this a known issue? Anyone have any thoughts on
I've set up our RT installation to redirect non-authenticated users to
a page that authenticates them, sets a cookie and updates a database,
and then redirects them to the RT 'home' page.
After the redirect users are sent to the RT login page, but it looks
weird. Our logo is scaled to be very lar
On 01/23/2014 11:44 PM, Christian Loos wrote:
Am 23.01.2014 20:18, schrieb Tim Wiley:
rt-4.0.13
We have a Queue A & Queue B.
Ticket A is in Queue A, and Ticket B is in Queue B.
User A has ModifyTicket on Queue A, but not on Queue B. User A would like to
make Ticket A refer to Ticket B, but
