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.
Gene At 08:14 AM 2/13/2009, Rob Munsch wrote: >I have queues, CFs, scrips and such set up more or less the way i want >them. For now. Until the department heads get back to me again. > >While configging things, i collected about 10k tickets into the >General queue in various stages of completeness. Other queues weren't >set up yet, CFs weren't being captured, etc. etc., so they remain in >General with empty CFs. > >What would be the least-painful way of running all 10k of them thru >the system as if they were being created, i.e. having all scrips apply >to them now that we would have wanted when they came it? > >Thanks, >Rob > >-- >/chown -R us:us /yourbase >_______________________________________________ >http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > >Community help: http://wiki.bestpractical.com >Commercial support: [email protected] > > >Discover RT's hidden secrets with RT Essentials from O'Reilly Media. >Buy a copy at http://rtbook.bestpractical.com -- 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: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
