Skip to content

feat(update_incident): Add custom_field_entries support#26

Open
JimmyWhitaker wants to merge 1 commit intoincident-io:mainfrom
JimmyWhitaker:feat/update-incident-custom-fields
Open

feat(update_incident): Add custom_field_entries support#26
JimmyWhitaker wants to merge 1 commit intoincident-io:mainfrom
JimmyWhitaker:feat/update-incident-custom-fields

Conversation

@JimmyWhitaker
Copy link

Summary

  • Exposes custom_field_entries in the update_incident MCP tool's InputSchema() and Execute() method
  • The client layer already supported custom field entries — this change bridges the gap in the handler layer
  • Adds unit tests for schema validation, parameter parsing, and edge cases (empty/invalid entries)

Motivation

The update_incident tool only supported updating name, summary, incident_status_id, and severity_id. This made it impossible to set custom field values (e.g., alert quality classifications) on incidents through the MCP tool, requiring manual UI updates.

Test plan

  • go build ./... passes
  • go test ./... passes (5 new tests added)
  • Verified end-to-end by setting a multi_select custom field on a live incident

🤖 Generated with Claude Code

The update_incident MCP tool previously only supported updating name,
summary, status, and severity. The underlying client already supported
custom field entries, but the handler layer didn't expose them.

This adds custom_field_entries to the InputSchema and Execute method,
enabling setting custom field values on incidents directly through the
MCP tool.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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