Ah, thanks everyone. I'll check configuration and look for this scrips (seems like someone before me already worked with them....)
On Tue, Aug 14, 2012 at 7:01 PM, Kevin Falcone <[email protected]>wrote: > On Tue, Aug 14, 2012 at 11:28:04AM -0400, Mike Johnson wrote: > > I don't believe Best Practical "built-in" any actions. They leave it > to clients to customize > > the RT instance to their own personal preferences. > > It is easy to put the scrips on to do what you are asking though. > > We don't build any in, but we do ship some defaults, as noted by Bill. > My assumption is that the OP disabled some along the way. > > > On Tue, Aug 14, 2012 at 10:43 AM, Jack Zabolotnyi <[1] > [email protected]> wrote: > > > > I thought it should be a default (built-in) action. Otherwise why > is it called AdminCC? > > > > On Tue, Aug 14, 2012 at 4:24 PM, Mike Johnson <[2] > [email protected]> wrote: > > > > You need a scrip to do that action I believe. > > Mike. > > > > On Tue, Aug 14, 2012 at 9:23 AM, Jack Zabolotnyi <[3] > [email protected]> wrote: > > > > Hi everyone. > > > > I have a little trouble: recepients set in AdminCC don't > receive any mails on ticket > > update (or any other events). Any other notification is doing > well. Should there be some > > permissions defined for this, or i miss something else? > > > > Thanks in advance for any help. :) > -- Jack Zabolotnyi Arces Network, LLC e: [email protected] w: http://www.arces.net PGP key: 2048R/7F2AB658 2012-07-02 PGP fingerprint: 4C7E 00A8 5210 F3D9 0509 C70E 87C8 666E 7F2A B658
