Skip to content

Show affected components on the incident page#363

Merged
jbrooksuk merged 5 commits into
mainfrom
feat/incident-affected-components
Jun 22, 2026
Merged

Show affected components on the incident page#363
jbrooksuk merged 5 commits into
mainfrom
feat/incident-affected-components

Conversation

@jbrooksuk

Copy link
Copy Markdown
Member

Adds a box at the top of the incident status page listing the components affected by that incident.

What

  • A new "Affected Components" box renders at the top of the incident page (status-page/incident.blade.php), above the incident detail.
  • Each affected component is rendered with the existing <x-cachet::component> Blade component, so rows look identical to the main status page (name, link, description popover, status badge).
  • The box only appears when the incident has components attached.
  • Added an affected_components_header translation key (en).

Notes

  • The controller already eager-loads $incident->components, so there's no extra query.
  • Reuses the same box styling as the component group/ungrouped boxes; all Tailwind classes are already in the compiled CSS, so no asset rebuild is required.

Tests

New tests/Feature/StatusPage/IncidentPageTest.php:

  • shows the affected components (and header) when components are attached;
  • hides the box when none are attached.

🤖 Generated with Claude Code

jbrooksuk and others added 5 commits June 17, 2026 18:22
Render the incident's affected components in a separate box at the top
of the incident status page, reusing the existing component Blade
component so each row matches the main status page. The box is only
shown when the incident has components attached.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Seed the demo incident with an affected component so the affected
components box renders out of the box.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add an optional hideStatus prop to the component Blade component and set
it when rendering the incident's affected components, so that box lists
the components without repeating each one's status.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@jbrooksuk jbrooksuk force-pushed the feat/incident-affected-components branch from e9bf26d to d1e0e50 Compare June 22, 2026 15:42
@jbrooksuk jbrooksuk merged commit d78c513 into main Jun 22, 2026
32 checks passed
@jbrooksuk jbrooksuk deleted the feat/incident-affected-components branch June 22, 2026 15:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant