Issue Summary

Statuspage incidents display different component names in the management UI and on the public page when components have been renamed after the incident was created.

In the incident management pane, the component name is shown as it was at the time of the incident, while on the public status page, the incident displays the component’s current (renamed) label. This difference makes it hard for admins to reason about historical incidents during component restructuring or planning.

Steps to Reproduce

1. Create a component on a Statuspage with any name. (Example 1)
2. Create an incident that affects this component and verify in the management UI that the incident lists the affected component as “Example 1”.
3. Rename the same component to a new name, e.g. “Example 2”.
4. Open the same incident in the Statuspage management UI and note the component name shown there.
5. Open the corresponding public incident page and compare the affected component name displayed to end users.

Expected Results

The affected component name for an incident should be consistent across the management UI and the public status page. Either:

1 - Both places should display the historical component name as it was at the time of the incident
or
2 - Both places should display the current (renamed) component name, according to the intended product behavior.

Actual Results

In the incident management page, the incident shows that it affected the historical component name (e.g. “Example 1”).

On the public status incident page, the same incident shows the current/renamed component for the same component ID (e.g. “Example 2”).

This leads to confusion when reviewing historical incidents and planning component restructures, because the same incident appears to reference different components depending on where it’s viewed.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.