opschain admin jsm-requests set-fields
integrations:jira-service-management
Adds/removes labels and sets issue fields on a JSM request through the audited write door. Fields take the Jira issue-edit shape as a JSON object; the audit event records field names only, never values.
opschain admin jsm-requests set-fields SUP-123 \
--add-label opschain --fields-json '{"priority": {"name": "High"}}'
Updated fields 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). |
--add-label <label> | A label to add (repeatable). |
--remove-label <label> | A label to remove (repeatable). |
--fields-json <json> | A JSON object of Jira issue fields to set, e.g. {"priority": {"name": "High"}}. |
See also
opschain docs cli/admin-jsm-requests-comment— leaving the context beside the change.