Re: [rt-users] Notify owners of new ticket not working
On 6/19/13 1:00 PM, Cena, Stephen (ext. 300) s...@qvii.com wrote: Ah; then it looks like it's a bug in the plug-in itself. It is in fact notifying the potential owners of a ticket, whether an Owner is specified or not. This isn't bad. I could just create a custom Template that would rework the email to let everyone know who has the ticket. Does anyone have a custom Scrip they use when a ticket is created, and no owner is specified that all potential owners get notified? I also need to look at the Perl modules someone recommended earlier, but I thought this plug-in might do the trick. My (working) custom condition: ### ## Custom condition for OnCreate ## Only applies if no owner is set ### return undef unless ( ($self-TransactionObj-Type eq Create) ( $self-TicketObj-Owner == $RT::Nobody-id ) ); return 1; Drew Barnes Software Applications Developer University of Cincinnati Blue Ash College Information Technology Department smime.p7s Description: S/MIME cryptographic signature
Re: [rt-users] RT 3.6.7 Default Templates
On 6/6/11 9:28 PM, Metz, Bobby bobby.m...@globalcrossing.commailto:bobby.m...@globalcrossing.com wrote: Hey all, I’m attempting to help our new RT admin figure out some oddities with an existing install. Some of his global templates, the default RT ones, were wiped and thus far I can’t seem to find their contents documented anywhere on-line. Having downloaded the 3.6.7 tarball I also don’t see any promising files or at least not any files with the syntax I’m expecting. I see several posts on-line from people seeking similar info but no answers. I’m hoping someone here can point us in the right direction, without suggesting a re-install. I’m expecting files with content similar to this: Greetings, You have just submitted a request to the { $Ticket-QueueObj-Name } ticket queue. Ticket Details -- Ticket Num: { $Ticket-Id } Queue: { $Ticket-QueueObj-Name } Subject: { $Ticket-Subject } Owner: { $Ticket-OwnerObj-Name } Status: { $Ticket-Status } Requestors: { $Transaction-CreatorObj-Name . ' ' . $Transaction-CreatorObj-EmailAddress . '' } Status: { $Ticket-Status } Request Details -- { $Transaction-Content } Or are they not stored in this format anywhere like this? Unpack the tarball and check etc/initialdata. Specifically the @Templates section. -- Drew Barnes Applications Analyst Network Resources Dept. Raymond Walters College
[rt-users] Setting TimeWorked in lifecycle
In our RT3.8.9 setup, I had customized the Tickets/Elements/Tabs to have a QuickResolve for when you could just look at a ticket and resolve it with no further action: for example, a known false positive virus alert, using: if ( $can{'ModifyTicket'} ) { if ( $Ticket-Status ne 'resolved' ) { $actions-{'Acc'} = { path = Ticket/Display.html?Status=resolvedid=$idUpdateTimeWorked=1, title = loc('Quick Resolve'), }; } } Now that RT 4 uses lifecycles, I'm not sure how to accomplish this same thing using lifecycles in RT_SiteConfig.pm. The documentation in RT_Config is less than helpful for anything but stock behavior: show the update page or just change a status, but it isn't very flexible beyond that. Am I missing something? Even a wiki page addressing lifecycles in some fashion? Thanks in advance for any help someone can give. Drew Barnes Applications Analyst Network Resources Dept. Raymond Walters College
Re: [rt-users] Cloning Solutions which work with version 3.8.8
On 3/4/11 3:45 AM, john s. firesk...@gmx.de wrote: Good morning System: Linux Ubuntu Server 10.04 RT Version: 3.8.8 with modperl I'm going to use some Solutions to clone or copy some Queues... so the creation of new queues would be much easier. Has someone any experience with tools which work well done? best regards john RT:Extension::QueueWizard -- Drew Barnes Applications Analyst Network Resources Dept. Raymond Walters College