Skip to content

Update incident components when recording an update - #481

Open
devmitulpatel wants to merge 2 commits into
cachethq:mainfrom
devmitulpatel:incident-update-components
Open

devmitulpatel wants to merge 2 commits into
cachethq:mainfrom
devmitulpatel:incident-update-components

Conversation

@devmitulpatel

Copy link
Copy Markdown

Closes #194.

Changes

  • CreateIncidentUpdateRequestData accepts an optional components array (component id and status), so the API can move component statuses when recording an update.
  • The CreateUpdate action syncs the incident's incident_components statuses: existing impacts are updated, components that are not impacted yet are attached, and components the update does not mention are left alone.
  • The Record update action preloads the incident's impacted components with their current status, so operators can move them on as part of the update message.

Verification

  • vendor/bin/pest — 1151 passed
  • vendor/bin/pint --test — clean
  • vendor/bin/phpstan analyse — no errors

Incident updates can now carry an optional list of impacted components
and the status to move them to. The CreateUpdate action syncs those
statuses without detaching components the update does not mention, and
attaches components that are not impacted yet.
The Record update modal now preloads the incident's impacted components
with their current status, so operators can move them on as part of the
update message.
@devmitulpatel

Copy link
Copy Markdown
Author

Screenshot of the Record update modal with the new Components section preloaded from the incident's current impact:

Record update modal

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.

Record Update on Incident missing Component

1 participant