You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An use case for ImportExportTicket is the merging of different OTRS/OTOBO/Znunx/KIX installations. In an ideal world this would be done in one smooth process and everything will be fine. In the real world imports are repeated because the requirements are changed. A simple example would be that more years and queues should be included. When there are already imported tickets in the new import then at least two problems can arise:
The imported ticket was already updated and the new import should not overwrite the changed attributes
Articles would be added again, leading to duplicate articles in the target system
Both of these cases can be alleviated by not importing tickets that already exist in the target system.
The text was updated successfully, but these errors were encountered:
Make it clear wether we deal with tickets, articles or both.
Add a variable that indicates wether the current line is a line
that only contains an article.
…pped
Usually there aren't any articles when AllowedOwnerInTarget is set. But one never
can be sure and at least on more import filter will be added soon.
From now on skipping means that an import filter has declined a change.
Tidying: use the variable $TicketUpdatedStatus in order to reduce the risk
of spelling errors
An use case for ImportExportTicket is the merging of different OTRS/OTOBO/Znunx/KIX installations. In an ideal world this would be done in one smooth process and everything will be fine. In the real world imports are repeated because the requirements are changed. A simple example would be that more years and queues should be included. When there are already imported tickets in the new import then at least two problems can arise:
Both of these cases can be alleviated by not importing tickets that already exist in the target system.
The text was updated successfully, but these errors were encountered: