Bug: Empty status in incident updates

[bakhterets]

Bug Report: Empty status in incident updates during specific impact sequence

Description

An issue occurs where a new component addition results in an empty status ("status": ""). This happens when a system incident is created via a component move, and a subsequent component is added automatically.

Steps to Reproduce

The bug is observed with the following impact sequence: 1 0 0 → 1 1 0 → 1 2 0 → 1 2 2.

1. Incident A (ID 289) is created with impact: 1 and status detected.
2. A component (Dedicated Host) is added to Incident A.
3. Incident B (ID 290) is automatically created with impact: 2 and system: true.
4. The component is moved from Incident A to Incident B. The first update in Incident B (ID 0) is correctly set to status: "SYSTEM".
5. A second component (Cloud Search Service) is added to Incident B.

Observed Behavior

The update for the second component addition has an empty status field:

{
  "id": 1,
  "status": "",
  "text": "Cloud Search Service (Big Data and Data Analysis, EU-DE, css) added to the incident by system.",
  "timestamp": "2026-02-10T10:26:13.186632Z"
}

Full example response:

{"data": [{"id": 290,
"title": "System incident from monitoring system",
"description": "System-wide incident affecting one or multiple components. Created automatically.",
"impact": 2,
"components": [170,
180

],
"start_date": "2026-02-10T10:25:55.076149Z",
"system": true,
"type": "incident",
"updates": [{"id": 0,
"status": "SYSTEM",
"text": "Dedicated Host (Compute, EU-DE, deh) moved from <a href='/incidents/289'>System incident from monitoring system</a>",
"timestamp": "2026-02-10T10:25:55.076149Z"

},
{"id": 1,
"status": "",
"text": "Cloud Search Service (Big Data and Data Analysis, EU-DE, css) added to the incident by system.",
"timestamp": "2026-02-10T10:26:13.186632Z"

}
]

},
{"id": 289,
"title": "System incident from monitoring system",
"description": "System-wide incident affecting one or multiple components. Created automatically.",
"impact": 1,
"components": [158

],
"start_date": "2026-02-10T10:24:37Z",
"system": true,
"type": "incident",
"updates": [{"id": 0,
"status": "detected",
"text": "The incident is detected.",
"timestamp": "2026-02-10T10:24:37Z"

},
{"id": 1,
"status": "detected",
"text": "Dedicated Host (Compute, EU-DE, deh) added to the incident by system.",
"timestamp": "2026-02-10T10:24:52.991633Z"

},
{"id": 2,
"status": "SYSTEM",
"text": "Dedicated Host (Compute, EU-DE, deh) moved to <a href='/incidents/290'>System incident from monitoring system</a>",
"timestamp": "2026-02-10T10:25:55.076149Z"

}
],
"status": "detected"
}
]
}

Expected Behavior:

The status should not be empty. We need to define whether the inherited/assigned status for this step should be SYSTEM or detected.

Environment Context

System Flag: true

Impact Sequence: 1 0 0, 1 1 0, 1 2 0, 1 2 2

[bakhterets]

The status should be like in a previous incident:
example:
incident_1.status(detected) -> incident_2.status(detected)