Skip to content

Commit

Permalink
Merge branch 'update-zendesk-example-config'
Browse files Browse the repository at this point in the history
  • Loading branch information
Jason Crome committed Sep 27, 2024
2 parents d840a0f + 0a06ff1 commit 34b8f3c
Showing 1 changed file with 17 additions and 3 deletions.
20 changes: 17 additions & 3 deletions lib/RT/Extension/Import/CSV.pm
Original file line number Diff line number Diff line change
Expand Up @@ -1828,6 +1828,16 @@ API. See L<this forum post|https://support.zendesk.com/hc/en-us/articles/4408882
Any of the default lists of tickets in Zendesk can be exported to CSV.
See the Zendesk documentation for more information.
=item RT Priority field must be customized
Zendesk priorities do not align 1:1 with RT's by default. The following
can be dropped into your RT configuration to match priorities between
the two systems:
Set(%PriorityAsString,
Default => { None => 0, Low => 25, Normal => 50, High => 75, Urgent => 100 },
);
=back
Exporting user information via the Zendesk API includes a bunch of
Expand Down Expand Up @@ -1869,8 +1879,12 @@ configuration:
'Requestor' => 'Requester',
'Created' => 'Requested',
'LastUpdated' => 'Updated',
'CF.Ticket Type' => 'Topic',
'CF.Channel' => 'Channel',
'CF.Topic' => 'Topic',
'Told' => 'Assignee updated',
'Priority' => sub {
my %priority = RT->Config->Get('PriorityAsString');
return $priority{ 'Default' }{ ($_[0]->{ 'Priority' }) };
},
);
Set( %CSVOptions, (
Expand All @@ -1879,7 +1893,7 @@ configuration:
escape_char => '',
) );
(you'll need to create two ticket custom fields: Ticket Type and Channel)
(you'll need to create a custom field named Topic)
If tickets were exported to a file named F<zendesk_tickets.csv>, the
following command will import tickets into your RT instance:
Expand Down

0 comments on commit 34b8f3c

Please sign in to comment.