Export Ticket Details

[ChrisMachnicki]

Hi All,
I was recently building a pyton script which automated an email using details from the DB and I hit a problem where the returned content of the ticket seemingly had a character limit and I could not extract all the details. I shelved this after looking for a while and assumed the details were being stored in blobs somewhere and outside the scope of what I can and cant do.

As we are in the process of moving away from OTRS to a paid for solution - the question has been raised again about how we can migrate the content and history of tickets into the new system maintaining both a history and some sort of redamentary reporting.

Is this possible? If so how?

Thanks

[reneeb]

It's possible, but that requires a lot of development. You have to map fields from OTRS to the fields in the other solution, you have to ensure that queues, states, users, ... already exist.

[ChrisMachnicki]

The mappings aren't a problem. I did it when I upgraded otrs and at the same time cleared it out of 4 years worth of crap. Whilst all the states, types, etc. aren't a problem it's the content of the tickets that are (these weren't an issue when migrating tot he same system)

[reneeb]

For all details, there are API methods http://otrs.perl-services.de/docs/. Use them...

* TicketGet
* ArticleGet
* HistoryGet
* ArticleAttachmentIndex
* ...

[ChrisMachnicki]

Is there a guide for setting up and using the API? I've used basic rest calls before with an addon client but only following the instructions of the application owners.
Where would I enter these -
my $Result = $OperationObject->Run(...