On Wed, Sep 14, 2016 at 2:48 PM, Scott Koch wrote:
> Thanks for the response, I think you may have misinterpreted my issue, see
> below. RT is hard to talk about due to the language overlap(English words
> and RT terms), so I may have said something confusing.
Okay. Sorry
Thanks for the response, I think you may have misinterpreted my issue, see
below. RT is hard to talk about due to the language overlap(English words
and RT terms), so I may have said something confusing.
On Wed, Sep 14, 2016 at 3:33 PM Matt Zagrabelny wrote:
> On Wed, Sep
On Wed, Sep 14, 2016 at 1:20 PM, Scott Koch wrote:
> RT Version: 4.2.12 (install has existed since 2003 and survived many major
> upgrades)
>
> Expected Behavior: When I move a existing ticket from one queue to another,
> the new queues AdminCCs will apply to that ticket for
RT Version: 4.2.12 (install has existed since 2003 and survived many major
upgrades)
Expected Behavior: When I move a existing ticket from one queue to another,
the new queues AdminCCs will apply to that ticket for future comments and
correspondences. I'm not expecting to see that particular
Vitaly,
Sorry for the typo. This is the code we use:
Condition: User Defined
Action: Notify AdminCcs
Template: Global template: Admin Correspond
Stage: TransactionBatch
Custom Condition Code:
# Set initial values
my $trans = $self-TransactionObj;
my $ticket = $self-TicketObj;
my
Thank you very much! I salute you, sir.
On 6/20/2011 8:40 PM, Kenneth Crocker wrote:
Sorry for the typo. This is the code we use:
--
Regards, Vitaly Tskhovrebov
Senior System Administrator
U.S. +1 (206) 905-9939
Russia +7 911 094-2035
2011 Training:
Hello.
I'm using group for AdminCC the queue. Eventually, member of AdminCC
created ticket, so he became requester. When owner of ticket reply him,
requestor receives duplicate email notification: one for requestor, and
the same for AdminCC. Is there any way to get rid of duplicate emails?
Hi,
As long as template and condition for notification scrips match then
it's recommended
to join them into one scrip. For example On C notify X with template T and
On C notify Y with template T get joined into On C notify X and Y
with template T.
On Sat, Jun 18, 2011 at 10:05 AM, Vitaly
Hi,
I studied more carefully the RT Essential book and RT online
resources... but I still have some doubts.
I'm guessing why RT send notification to the admincc only via BCC. What
is the real reason behind this behaviour?
I supposed the goal is to not to expose the mail address to CC,
In what RT database table is the 'AdminCC' of the ticket information is
stored. I want to add 'AdminCC's' to a ticket from an external
application.
Thanks
Naweed Ahmed
-
The information contained in this e-mail message is intended only
for the
Naweed,
AdminCc's are basicallt identified as groups and there are relationships
with ACL, GroupMembers Tickets.
I'd advise having your external system just send an email to the correct
ticket and use CommandByMail to add an AdminCc. That way, RT will keep
everything in sync.
Kenn
LBNL
On
Or you can use the REST interface:
http://requesttracker.wikia.com/wiki/REST
-Chris
Am 25.11.2010 00:48, schrieb Kenneth Crocker:
Naweed,
AdminCc's are basicallt identified as groups and there are relationships
with ACL, GroupMembers Tickets.
I'd advise having your external system just
I can seem to find the right way to accomplish this:
I have my groups as adminCCs for their respective queues so that they get
notified when tickets get created which is working great, however once a tech
picks up a ticket I do not want everyone getting notified on ticket
correspondence, I see
Steve,
Modify the scrip as to who gets the notification.
Kenn
LBNL
On Thu, Oct 21, 2010 at 9:49 AM, Steve O'Brien steve.obr...@hdesd.orgwrote:
I can seem to find the right way to accomplish this:
I have my groups as adminCCs for their respective queues so that they get
notified when
Hi,
I have a new RT 3.8.8 install setup on Fedora 12.
All users seem to have the Queues I'm an Admin CC For on their RT at a
Glance screen, but this is not listed in their preferences, nor the user,
group or Global RT at a Glance preferences. Where else is this option set
please?
Thanks
I'm having a little bit of trouble with the AdminCC failing to get created. I
am using RT:Authen::ExternalAuth. Everything is well there I've verified that
is working correctly.
When I add/create and admincc for a user that has not logged into RT the user
does not get created automatically.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've got a pretty weird problem going on here.
I have the group Admins set as the AdminCC watcher for all my queues.
When I create a ticket the members of the group get the AdminCC ticket
created template, but they are not added as AdminCCs under
Hi Matt,
I don't think the Queue AdminCcs show up within tickets. They don't on my
system, but they do get the mail that they are supposed to get. I'm pretty
sure that the people entries would only show watchers that have been
added to the ticket via a script or the ticket's People tab.
Matt,
I'm in agreement with Gene. Being added to the Ticket adminccc has
nothing to do with getting notifications on future updates. As to why
they are not getting any update info notifications, what scrips have you
set up to do that?
Kenn
LBNL
On 2/25/2008 11:31 AM, Gene LeDuc
Steve,
There are many reasons this might happen. What are the privileges you
have allowed for the AdminCc and Requestor Roles? Are the same UserId's
in any groups that are getting notifications? What Global/Queue Scrips
have you set up and where are they sent? Without that info, it will be
Hi all,
Is there a difference in the way RT 3.6.1 handles Watchers for comments?
If I'm the requestor for a ticket and comment on it, I don't get an
e-mail notification. I seem to recall it doing this in the past, and I
actually preferred it that way so I can archive my e-mail for record
21 matches
Mail list logo