[rt-users] import 1.0 to 2.0 issue with custom transaction types

Bill Petrisko bill at limelightnetworks.COM
Fri Dec 14 20:00:00 EST 2001

Ok... I am attempting to import my old rt1.0 database into rt2.0, and am
running across the following issue:

I created a custom transaction type in rt1.0 (yes, I know I shouldn't have
done this) called 'notify'.  This is inserted by an external program (using
the webrt add_transaction) whenever my external paging script notified
someone about an open ticket.

Now, seeing as how I have learned my lesson about modifying code that is not
stale/un-upgradable (thought I would never upgrade to 2.x, so why not hack
the heck out of 1.07?) - can someone offer me advice on modifying
import-1.0-to-2.0 to deal with this unrecognized transaction type?  Yes, I
can modify it to just throw away these items, but I would like them included
as a comment.

Basically, what I need is to insert a routine around line 543 of
import-1.0-to-2.0, as such:

        elsif ( $row->{type} eq 'notify' ) {
            $trans_args{'Type'} = "Comment";
            # routine to add comment text of:  "Notification by
".$row{'actor'}.": ".$row{'trans_data'}



More information about the rt-users mailing list