Hi everybody,
since yesterday I'm struggling with the Approval system of RT. I tried
several systems and solutions from the mailing list and the wiki but I
got nothing to work completely.
We are using RT in an international developer group in our company for
posting bugfixes etc. I have set up
I use this so that people can the ten newest in each queue they have
rights to.
http://wiki.bestpractical.com/view/TicketsPerQueue
Liam R. MacInnes wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sam Tilders
Sent: Thursday, August 30, 2007 2:56
Hi all.
We want to enhance RT by these tasks:
1. Allow anonymous ticket approval. In other words, we create ticket,
send it to the user. Ticket has some URL in the body, like:
https://rt.company.com/approve?hash=TICKETHASH
So, when user receive ticket, he click on the URL and ticket become
I've found out, that to be approved tickets will be visible if they
are owned by somebody. At least he will see the tickets at the Approval
site then. But that's also not like it's supposed to work, is it?
Benjamin Weser wrote:
Hi everybody,
since yesterday I'm struggling with the Approval
Peer Michael schrieb:
It's seems, that your Autoreply script isn't a global script, but a script,
that runs only in a specific queue.
So? Of course it's a local scrip, I need a different autoreply template for each
of my queues.
Regards,
--ck
--
http://www.de-punkt.de [ [EMAIL
I am exploring RTFM for the first time and just installed 2.2RC5 along
with RT 3.6.4. Questions/observations:
1. Topics. I see there is something called Topics that is not covered
in the documentation. These appear to act like tags and cut across RTFM
Classes as a secondary way of classifying
Hi,
I really need a solution to this problem ASAP, our complete ticketing has ground
to a halt. How can it happen that only a completely new requestor (not known to
RT before) receives the initial autoreply and all correspondence via e-mail, but
all known requestors don't receive anything *at
Hi,
the rt debug log looks like this during one of the broken transactions:
[Fri Aug 31 14:26:21 2007] [debug]: About to commit scrips for transaction
#324709 (/usr/local/rt/lib/RT/Transaction_Overlay.pm:173)
[Fri Aug 31 14:26:21 2007] [info]:
[EMAIL PROTECTED] #59902/324709 - Scrip 7
