What happends with SLA when the CI changes for an ongoing incident?

[TobiasAdel]

When an incident ticket is created and a CI is identified as tarkget for incident, an SLA task is created if an SLA si defined for that CI. (Is that a correct understanding?)
Question: what happends if the CI was not correct from the beginning, and we update the CI, which have a different SLA defined?
Is it at all possible?
What happen to the old SLA task ongoing for the first CI
Is a new SLA task created and if so, will it inherit the parameters from the old SLA task?

[Dr Atul G- LNG · Accepted solution]

Hi @TobiasAdel 

When an incident ticket is created and a CI is identified as the incident's target, an SLA task is created if an SLA is defined for that CI. (Is that a correct understanding?)

Atul: It depends. In practice, SLAs are defined based on priority, but in a few cases, if required, you can define SLAs based on or in combination with CI as well.
Question: What happens if the CI was not correct from the beginning and we update it, which has a different SLA defined?

Atul: SLA has 4 parts, Start, Hold, Stop and Resume conditions. It depends on which section of SLA you are using the CI. Also, SLA works on conditions, if the conditions do not match SLA will not attached.
Is it at all possible?

Atul: Yes.
What happened to the old SLA task ongoing for the first CI

Atul: It depends, whether you want to stop or hold or cancel the old SLA.
Is a new SLA task created and if so, will it inherit the parameters from the old SLA task?

Atul: It depends, if you are using Retroactive Start or not.