I need to migrate from our homegrown ticketing system to RT. The
general model is similar – a table of tickets, and then a table of
email messages or log entries each associated with a ticket.
Migrating the table of tickets is straightforward, but I’m having a
hard time getting my brane around the log entries. I see that
import-1.0-to-2.0 calls RT::Transaction::Create() directly, but
I also see that the documentation for RT::Transaction::Create() notes
that it should never be used directly, but should only be accessed via
the published RT::Ticket API.
Is that just an RT-migration-specific bit in import-1.0-to-2.0, or
should I use it as an example?
-Rich
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------
Ideally, we’d have an RT::Transaction::Import() method. In the meantime,
well, it’s a case of “if you do this, you’re responsible for a lot of
integrity checking ,etc” which is why the docs tell you not to do it.
import-1.0-to-2.0 is a reasonable template for moving from
a crufty, hacky, poorly designed ticketing system to RT2. ;)On Thu, May 02, 2002 at 02:45:00PM -0400, Rich Lafferty wrote:
I need to migrate from our homegrown ticketing system to RT. The
general model is similar – a table of tickets, and then a table of
email messages or log entries each associated with a ticket.
Migrating the table of tickets is straightforward, but I’m having a
hard time getting my brane around the log entries. I see that
import-1.0-to-2.0 calls RT::Transaction::Create() directly, but
I also see that the documentation for RT::Transaction::Create() notes
that it should never be used directly, but should only be accessed via
the published RT::Ticket API.
Is that just an RT-migration-specific bit in import-1.0-to-2.0, or
should I use it as an example?
-Rich
–
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.
Ideally, we’d have an RT::Transaction::Import() method. In the meantime,
well, it’s a case of “if you do this, you’re responsible for a lot of
integrity checking ,etc” which is why the docs tell you not to do it.
Is there anything specific that I should expect to bite me there, or
just a lot of generalist teeth?
import-1.0-to-2.0 is a reasonable template for moving from
a crufty, hacky, poorly designed ticketing system to RT2. 
What a coincidence! That’s what I have! 
While I’m puzzling over migration: If I call
$ticket->Create(id => 5, …)
where there’s no ticket #5 yet but there are tickets >5, it still
creates the next ticket per auto_increment. Import() works as
expected. Is that a documentation bug or a code bug?
-Rich
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------
Is there anything specific that I should expect to bite me there, or
just a lot of generalist teeth?
Just some teeth. Of varying levels of pointiness.
While I’m puzzling over migration: If I call
$ticket->Create(id => 5, …)
where there’s no ticket #5 yet but there are tickets >5, it still
creates the next ticket per auto_increment. Import() works as
expected. Is that a documentation bug or a code bug?
Doc bug. Create shouldn’t take an Id. submit something to rt-2.0-bugs?
-Rich
–
Rich Lafferty --------------±----------------------------------------------
Ottawa, Ontario, Canada | Save the Pacific Northwest Tree Octopus!
http://www.lafferty.ca/ | Save The Pacific Northwest Tree Octopus
rich@lafferty.ca -----------±----------------------------------------------
rt-devel mailing list
rt-devel@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-devel
http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.