Hi Ken,<br><br>I would have never looked at the Offline option lol, thought it was something completely different, I'l have a go at that one!<br><br>I also just currently bumped into this commandline argument which might also help me out in a similar way:<br>
<br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">$ rt create -t ticket set subject="urgent contact request" set queue=general<br>
</blockquote><br>It's an example which creates 1 ticket with 1 command, I could add some extra values to it to complete the lot but it looks like the Offline option does about the same in an easier format.<br><br>Thanks for the tip.<br>
<br clear="all">Best regards,<br><br>Bart<br><br>
<br><br><div class="gmail_quote">2011/6/6 <a href="mailto:ktm@rice.edu">ktm@rice.edu</a> <span dir="ltr"><<a href="mailto:ktm@rice.edu">ktm@rice.edu</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On Mon, Jun 06, 2011 at 01:44:01PM +0200, Bart wrote:<br>
> Hi,<br>
><br>
> We are currently working on migrating to Request Tracker.<br>
><br>
> The step on which we are now is creating a proof of concept, this is coming<br>
> along pretty nicely.<br>
> With the O'Reilly book + mailing lists + wiki at hand we're getting there,<br>
> just filling out the specific details :)<br>
><br>
> I do however want to look at a road bump ahead, which is migrating the old<br>
> ticket date into RT.<br>
><br>
> We have the ability to export all the current date to CSV format, keeping<br>
> those fields that we feel are fit for RT. (the old/current ticketing system<br>
> is Assyst from Axios Systems)<br>
> We don't mind if ticket numbers are new, we prefer it really, as long as we<br>
> can store the old ticket number in a CF (which I believe we can).<br>
><br>
> What would be the best way to import the data?<br>
> Can we use the command-line RT functions or do we have to do some database<br>
> magic? (I'm not a database wizard so we'd have to find someone for that lol)<br>
><br>
> The reason why I'm asking this is mainly to get some information about the<br>
> migration process before hand, such information would safe me allot of time<br>
> later on.<br>
><br>
> So any information that would point us in the right direction would be<br>
> helpful.<br>
><br>
> Thanks in advance.<br>
><br>
> Best regards,<br>
><br>
> Bart<br>
<br>
</div></div>Hi Bart,<br>
<br>
I would take a look at the Tools->Offline and see if you can generate<br>
an appropriate text file for import from your CSV. I used that method<br>
to create several thousand tickets at one shot.<br>
<br>
Cheers,<br>
Ken<br>
</blockquote></div><br>