Skip to content

Feature request: set custom form fields on incidents create/update #64

Description

@minkimipt

Use case

Creating an incident or maintenance from a script with the workspace's custom form fields filled in, the same as the UI dialog.

What's missing

incidents create / incidents update have flags for built-in attributes (--services, --types, --environments, --teams, …) but no way to set custom form fields. There is no --field style flag, and custom field values aren't read back by incidents get either.

Why it matters

Workspaces use required custom fields to drive status-page templates and workflows — in ours, a planned maintenance needs a software version and a rollout date, and the status-page announcement template interpolates them (the version builds a changelog link). A CLI-created incident without them either fails the workspace's requirements or publishes a broken announcement, so the create step still has to go through the UI.

Proposed

rootly incidents create --title="..." --field sw_version=2.30.2 --field rollout_date=2026-10-05
rootly incidents update <id> --field rollout_date=2026-10-06
rootly incidents get <id> --format=json   # includes custom field values

Keyed by the form field slug, repeatable. Discovery could follow the existing pattern (rootly form-fields list), like services list / teams list.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions