ReplyToTicket right and pay attention to NotifyActor config option.
Sure you'll need scrip notify requestors on correspond with template
xxx.
On Mon, Feb 16, 2009 at 1:45 PM, Jon Westholm jon.westh...@cint.com wrote:
Hi all,
Total freshmen to RT and setting up my first instance that should run
Hi,
somebody here merged a ticket with another one, but shouldn't have. Is it
possible to split the tickets again?
Thanks
--
Mathieu Longtin
1-514-803-8977
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help:
On Mon, Feb 16, 2009 at 12:20:38PM -0500, Mathieu Longtin wrote:
Hi,
somebody here merged a ticket with another one, but shouldn't have. Is it
possible to split the tickets again?
It's a bit difficult but possible in the DB. See the FAQ entry on this
at http://wiki.bestpractical.com/.
On Thu, Jan 29, 2009 at 05:41:57PM +0100, Lars Kristian Klykken wrote:
Users are properly authenticated on the web interface, and they also
have no problem sending mail to RT, as long as they're using the email
address defined in RT at createtime (or modified manually in the
preferences), but
OK. I was able to solve the last problem here as well!
I went to *rt3/share/html/Elements/QueueSummary* and added *OR Status =
'staged'* to the following line:
% my $all_q = $queue_cond . (Status = 'open' OR Status = 'new' OR Status
= 'stalled' OR Status = 'staged');
I imagine this isn't the
On Mon, Feb 16, 2009 at 15:04, Chris Nelson cnel...@delivra.com wrote:
to the bottom of rt3/lib/RT/I18N/en.po, restarted apache, and it worked like
a champ! Is there a way to get RT to use the en_qaa.po file so that upgrades
won't destroy those changes?
Yes, you have to set your language to
Chris Nelson wrote:
OK. I was able to solve the last problem here as well!
I went to *rt3/share/html/Elements/QueueSummary* and added *OR Status
= 'staged'* to the following line:
% my $all_q = $queue_cond . (Status = 'open' OR Status = 'new' OR
Status = 'stalled' OR Status = 'staged');
I am working on some code in ruby that accesses the REST interface. I am
running RT 3.8.2. I am able to login, save cookies, and retrieve tickets
and history without problems.
My problem starts when I try to use REST to add a comment/correspondence to
a ticket. The following code:
Tom Lahti wrote:
I am working on some code in ruby that accesses the REST interface.
I've re-written the whole thing using the rest_client ruby gem, and
essentially the same results, but I get more info out of what's going on:
# ./resttest2.rb
- Request headers
Here's the scenario:
1) A User has a custom field called Billable with two choices, yes, and
no.
2) User creates ticket
3) Scrip checks Billable and sets ticket billable if user is billable
I'm having a bit of trouble figuring out how I can access the custom field
belonging
no value sent for required parameter 'changes'
Stack:
[/opt/rt38/share/html/REST/1.0/dhandler:285]
[/opt/rt38/share/html/REST/1.0/autohandler:54]
[/opt/rt38/share/html/autohandler:311]
I seem to have figured this out. You can use
application/x-www-form-urlencoded, but you have to
11 matches
Mail list logo