1 INCIDENT or 2

[MALIZIOSOG]

We recently had a network change that was executed.  As a result we had 2 events that were raised due to broken functionality following the change.  Is the right thing to do for tracking purposes, to open 1 incident record for each event even through they were both caused and resolved by rolling back the change or should we have 1 incident, tied to the single change that was rolled back, noting each of the events or impacts that occurred as a result? 

[Pradeep Thipani]

Hi @MALIZIOSOG,

You can raise a single incident for this issue, as it was caused by only one change. However, if there are dependencies on other events, you may want to create a child incident linked to the main incident for better tracking.

Thanks,

Pradeep

[MALIZIOSOG]

thanks.  This was the approach we took.