opschain admin jsm-requests transition
integrations:jira-service-management
Moves a JSM request through a workflow transition, named by its
transition name (matched case-insensitively against the request's
available transitions) or numeric id. An unknown transition refuses by
name, listing what is available. An optional --comment lands as a JSM
internal note on the transition.
opschain admin jsm-requests transition SUP-123 "In Progress"
Transitioned SUP-123 via In Progress
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). |
--comment <text> | An internal note recorded with the transition. |
See also
opschain docs cli/admin-jsm-requests-resolve— resolving with evidence attached.