RT2 to RT3 migration tool v1.8 problem

RT Users
1

All-
My import works much better now with version 1.8. It runs with no erros
for about 24 hours, and then after inserting all 14029 tickets, it fails with
the following:

.t-14028
.t-14029
Importing links
Could not create scrip: On Owner Change Notify Owner with templateOwner
Change in queue0
Could not create scrip: On Create Autoreply To Requestors with
templateAutoresponce- Critical in queue16
Could not create scrip: On Create Notify Owner with template
transaction-critical in queue16 – $VAR1 = {
‘Description’ => ‘Imported from RT 2.0’,
‘ScripCondition’ => ‘On Create’,
‘Template’ => ‘transaction-critical’,
‘Queue’ => ‘16’,
‘ScripAction’ => ‘Notify Owner’
};

Could not create scrip: On Create Notify Requestors, Ccs and AdminCcs with
templatetransaction-critical in queue16

2

Hi,

Does anyone know if RT will work/coexist with Microsoft Exchange?

Thanks,

./mike

3

All-
My import works much better now with version 1.8. It runs with no erros
for about 24 hours, and then after inserting all 14029 tickets, it fails with
the following:

Those “errors” are RT reporting to you that it could not import your
custom scrips. this is normal and correct. You’ll want to hand-create
those scrips and templates.

.t-14028
.t-14029
Importing links
Could not create scrip: On Owner Change Notify Owner with templateOwner
Change in queue0
Could not create scrip: On Create Autoreply To Requestors with
templateAutoresponce- Critical in queue16
Could not create scrip: On Create Notify Owner with template
transaction-critical in queue16 – $VAR1 = {
‘Description’ => ‘Imported from RT 2.0’,
‘ScripCondition’ => ‘On Create’,
‘Template’ => ‘transaction-critical’,
‘Queue’ => ‘16’,
‘ScripAction’ => ‘Notify Owner’
};

Could not create scrip: On Create Notify Requestors, Ccs and AdminCcs with
templatetransaction-critical in queue16

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

4

Jesse,

Could you give me/the list some pointers on recreating custom scripts?

I think it would be ideal if I could create it via the web interface, but I
have no idea where to start from.

-Jamie

5

Thanks, I will do that. Is the import script expected to due any other tasks
after importing scrips or did it fail at the end of the script? If this was
not the last task, how can I tell the importer to ignore scips and continue?

JonOn Thursday 10 April 2003 11:59 am, Jesse Vincent wrote:

On Thu, Apr 10, 2003 at 10:45:27AM -0400, Jon Hittner wrote:

All-
My import works much better now with version 1.8. It runs with no
erros for about 24 hours, and then after inserting all 14029 tickets, it
fails with the following:

Those “errors” are RT reporting to you that it could not import your
custom scrips. this is normal and correct. You’ll want to hand-create
those scrips and templates.

.t-14028
.t-14029
Importing links
Could not create scrip: On Owner Change Notify Owner with templateOwner
Change in queue0
Could not create scrip: On Create Autoreply To Requestors with
templateAutoresponce- Critical in queue16
Could not create scrip: On Create Notify Owner with template
transaction-critical in queue16 – $VAR1 = {
‘Description’ => ‘Imported from RT 2.0’,
‘ScripCondition’ => ‘On Create’,
‘Template’ => ‘transaction-critical’,
‘Queue’ => ‘16’,
‘ScripAction’ => ‘Notify Owner’
};

Could not create scrip: On Create Notify Requestors, Ccs and AdminCcs
with templatetransaction-critical in queue16

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

6

The things it did not do, it didn’t do before importing all your
tickets, iirc. That was an end of run report, not it bombing out.On Thu, Apr 10, 2003 at 12:09:21PM -0400, Jon Hittner wrote:

Thanks, I will do that. Is the import script expected to due any other tasks
after importing scrips or did it fail at the end of the script? If this was
not the last task, how can I tell the importer to ignore scips and continue?

Jon

On Thursday 10 April 2003 11:59 am, Jesse Vincent wrote:

On Thu, Apr 10, 2003 at 10:45:27AM -0400, Jon Hittner wrote:

All-
My import works much better now with version 1.8. It runs with no
erros for about 24 hours, and then after inserting all 14029 tickets, it
fails with the following:

Those “errors” are RT reporting to you that it could not import your
custom scrips. this is normal and correct. You’ll want to hand-create
those scrips and templates.

.t-14028
.t-14029
Importing links
Could not create scrip: On Owner Change Notify Owner with templateOwner
Change in queue0
Could not create scrip: On Create Autoreply To Requestors with
templateAutoresponce- Critical in queue16
Could not create scrip: On Create Notify Owner with template
transaction-critical in queue16 – $VAR1 = {
‘Description’ => ‘Imported from RT 2.0’,
‘ScripCondition’ => ‘On Create’,
‘Template’ => ‘transaction-critical’,
‘Queue’ => ‘16’,
‘ScripAction’ => ‘Notify Owner’
};

Could not create scrip: On Create Notify Requestors, Ccs and AdminCcs
with templatetransaction-critical in queue16

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

7

Jesse,

Could you give me/the list some pointers on recreating custom scripts?

I think it would be ideal if I could create it via the web interface, but I
have no idea where to start from.

No, but I can refer you to the documentation, which is linked from

Jesse

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.