Thank you for your reply. I should have been more specific :)
Actually we are trying to migrate "resolved and closed" tickets into iTOP.
When I try to import them with past start date we got something like:
ERROR: 2020-02-27 00:00:00
Could not be changed to 2020-02-27 00:00:00 - reason: The attribute 'start_date' is read-only and cannot be modified (current value: , proposed value: 2020-02-27 00:00:00
So, I understand that some fields are "read-only", but is it possible to modify this to import closed tickets?
This is to consolidate info for audit purpose.
thank you
Chris
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am afraid that the CSV import, does control the lifecycle constrains, so prevent such import. There is just one methods which work, use REST/JSON api, that method can create / modify objects without going through the UI datamodel and lifecycle checks.
Datasynchro does take into account lifecycle fields constrains, I was wrong.
Last edit: Vincent @ Combodo 2020-10-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
as part of the itop integration. we need to add tickets from an other system.
how is it possible to add tickets with spefic dates?
thanks
Hi Chris,
Did you try to import them using the CSV import feature?
Guillaume
Hi Guillaume,
Thank you for your reply. I should have been more specific :)
Actually we are trying to migrate "resolved and closed" tickets into iTOP.
When I try to import them with past start date we got something like:
ERROR: 2020-02-27 00:00:00
Could not be changed to 2020-02-27 00:00:00 - reason: The attribute 'start_date' is read-only and cannot be modified (current value: , proposed value: 2020-02-27 00:00:00
So, I understand that some fields are "read-only", but is it possible to modify this to import closed tickets?
This is to consolidate info for audit purpose.
thank you
Chris
I am afraid that the CSV import, does control the lifecycle constrains, so prevent such import. There is just one methods which work, use REST/JSON api, that method can create / modify objects without going through the UI datamodel and lifecycle checks.
Datasynchro does take into account lifecycle fields constrains, I was wrong.
Last edit: Vincent @ Combodo 2020-10-06
I have modified my first reply which was partially wrong...