opschain admin jsm-requests comment

integrations:jira-service-management

Posts one comment on a JSM request through the audited write door. The comment is always a JSM internal note — the wire call hardwires the internal flag and there is no flag to make it customer-visible. The request must sit inside the connection's project scope.

opschain admin jsm-requests comment SUP-123 --body "Triage: reproduced on 5.4; fix queued."
Posted internal comment 10042 on SUP-123

Flags

Flag	Meaning
--server <url>	Server base URL (default: the active context / OPSCHAIN_SERVER).
--auth-token <token>	Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login).
--connection <code-or-id>	The JSM connection to write through (default: the single enabled connection).
--body <text>	The internal note's text (required).

See also

• opschain docs cli/admin-jsm-requests-resolve — the evidence-linked resolution.