Hi,
I found out that I geht douple entries in attribute private_log if I use a clone rule in this extension.
This problem is only in version 1.3.5.
Version 1.3.4 and even version 1.3.2 do not behave like this.
I tested it even on a clean iTop-installation.
This is the rule i used for test purposes:
17 =>
array (
'source_scope' => 'SELECT UserRequest',
'allowed_profiles' => 'Administrator, Service Desk Agent',
'menu_label/EN US' => 'TEST CLONE to new Incident',
'form_label/EN US' => 'Cloning to Incident with data from original Request: %1$s The original Request will automatically be closed!!',
'dest_class' => 'Incident',
'preset' =>
array (
0 => 'clone(caller_id,org_id,title,description,origin,impact,urgency,priority)',
1 => 'clone(private_log)',
2 => 'set(private_log, Created from original Request: $this->hyperlink()$)',
),
'retrofit' =>
array (
1 => 'append(private_log, CLONED to Incident: $this->hyperlink()$)',
),
),
If I now clone a userrequest to an incident I get the private_log entry twice as seen in the screenshot.
Is this a known problem?
Thanks,
best regards,
Nico
Hi,
I found out that I geht douple entries in attribute private_log if I use a clone rule in this extension.
This problem is only in version 1.3.5.
Version 1.3.4 and even version 1.3.2 do not behave like this.
I tested it even on a clean iTop-installation.
This is the rule i used for test purposes:
If I now clone a userrequest to an incident I get the private_log entry twice as seen in the screenshot.
Is this a known problem?
Thanks,
best regards,
Nico
Yes, it's a known issue which is fixed in Git on tag 1.3.6 of the itop-object-copier module but no build created yet...