[rt-users] Fwd: Retroactive scrip-ing
forgot to cc the list again :P itchy send finger, sorry Gene. On Fri, Feb 13, 2009 at 11:41 AM, Gene LeDuc gle...@mail.sdsu.edu wrote: I think I'd write a perl script to read each ticket and then e-mail it back to RT. Not very elegant and a significant bump in your mail server's workload, but you know that they would all be treated as new tickets. This should be a pretty trivial script to write using the API. Mail server's not working very hard right now, so that shouldn't be a problem. If i follow this right, this will create a new set of tickets with what i want, but the originals will still remain as-is, yes? I suppose i could destroy the originals after i verify it worked. Thanks, i'll take a poke at this. -- /chown -R us:us /yourbase ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Fwd: Retroactive scrip-ing
If i follow this right, this will create a new set of tickets with what i want, but the originals will still remain as-is, yes? I suppose i could destroy the originals after i verify it worked. Better to merge I should think, if you're going this route. Especially since you're also going to be sending out lots of requestor notifications, which could be potentially confusing e.g; It's already done, why are you bugging me again? or replying to an old message with the old ticket ID. -- Cambridge Energy Alliance: Save money. Save the planet. ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Fwd: Retroactive scrip-ing
Disable all scrips that send correspondence, go one step further and shut down your MTA (so that mail sent in will try again later), use the API to re-run those transactions, re-enable scrips, start the MTA back up. No emailings, no fuss. Jerrad Pierce wrote: If i follow this right, this will create a new set of tickets with what i want, but the originals will still remain as-is, yes? I suppose i could destroy the originals after i verify it worked. Better to merge I should think, if you're going this route. Especially since you're also going to be sending out lots of requestor notifications, which could be potentially confusing e.g; It's already done, why are you bugging me again? or replying to an old message with the old ticket ID. -- Drew Barnes Applications Analyst Network Resources Department Raymond Walters College University of Cincinnati ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Fwd: Retroactive scrip-ing
On Fri, Feb 13, 2009 at 1:48 PM, Drew Barnes barne...@ucrwcu.rwc.uc.edu wrote: use the API to re-run those transactions I have to confess, after some time googling and looking over the wiki, that i cannot figure out how to do that :(. -- /chown -R us:us /yourbase ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Fwd: Retroactive scrip-ing
If you speak perl, I'll be happy to send you a copy of a script we use that would illustrate getting ticket info using the API. If you don't speak perl, then I wouldn't recommend learning it with this script or this project. At 02:17 PM 2/13/2009, Rob Munsch wrote: On Fri, Feb 13, 2009 at 1:48 PM, Drew Barnes barne...@ucrwcu.rwc.uc.edu wrote: use the API to re-run those transactions I have to confess, after some time googling and looking over the wiki, that i cannot figure out how to do that :(. -- /chown -R us:us /yourbase -- Gene LeDuc, GSEC Security Analyst San Diego State University ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
Re: [rt-users] Fwd: Retroactive scrip-ing
I speak it well enough to modify things, so far. I wouldn't call myself fluent, but i can more than copy-paste code. I'd love to see it. This system isn't in production yet, so i don't mind potential breakage trying to get something to work. Thanks! On Fri, Feb 13, 2009 at 6:18 PM, Gene LeDuc gle...@mail.sdsu.edu wrote: If you speak perl, I'll be happy to send you a copy of a script we use that would illustrate getting ticket info using the API. If you don't speak perl, then I wouldn't recommend learning it with this script or this project. At 02:17 PM 2/13/2009, Rob Munsch wrote: On Fri, Feb 13, 2009 at 1:48 PM, Drew Barnes barne...@ucrwcu.rwc.uc.edu wrote: use the API to re-run those transactions I have to confess, after some time googling and looking over the wiki, that i cannot figure out how to do that :(. -- /chown -R us:us /yourbase -- Gene LeDuc, GSEC Security Analyst San Diego State University -- /chown -R us:us /yourbase ___ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com