GLPI 10.0.18 Issue when cloning tickets

[Artur-Andrade-B]

I've had some issues when dealing with cloned taks, specifically about the SLA of the cloned tickets.

So i've set up a GLPI on my organization, where it is currently being used for IT support to that organization, there's a few cases where the task needs to go through multiple different teams, needing to have atleast one task per team.

The initial idea was to clone the Task and send that cloned task to another team whilst linking both, what happens when that procedure is done is that both the creation date and the SLA of the original task are also cloned, so both tickets end up with the same current SLA, that meaning if the original task has 3 hours left to violate the sla the second cloned task also begins it's lifecycle with 3 hours left, even though it should start the timer again.

A basic visualization if my explanation is too convoluted would be like this:

Current Result:

[Original] Ticket: 001 / SLA: 8 hours / current SLA: 3 hours left

[Cloned] Ticket: 002 / SLA: 8 hours / current SLA: 3 hours left

Expected Result:

[Original] Ticket: 001 / SLA: 8 hours / current SLA: 3 hours left

[Cloned] Ticket: 002 / SLA: 8 hours / current SLA: 8 hours left

I would like to know if there's any way to configure that so that could give that functionality.
I'm still very new to GLPI and the whole usage of plugins, so there's still a lot that i don't really know, if there's any other piece of information that i can give to help in solving this behavior please let me know.