opschain admin jsm-requests resolve

integrations:jira-service-management

Resolves a JSM request with evidence links, in one audited write:

1. records the typed jsm:request reference (relationship resolves) on the resolving change or workflow run's governance metadata block — existing references are merged, never dropped;
2. posts one internal evidence comment carrying the OpsChain provenance (subject, target, action) and the supplied evidence links;
3. performs the resolving transition.

The OpsChain ledger stays the source of truth — what JSM receives is a copy with provenance. The resolving subject must carry a governance checklist you may read.

opschain admin jsm-requests resolve SUP-123 \
  --run 0193f0a2-… --transition Resolve \
  --evidence-url https://opschain.example/changes/0193f0a2-…
Resolved SUP-123 via 0193f0a2-… (Resolve) — typed reference recorded, evidence comment 10043 posted

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).
--run <id>	The resolving OpsChain change or workflow run id (required).
--transition <name-or-id>	The JSM transition that resolves the request (required).
--comment <text>	Extra resolution text, prepended to the evidence comment.
--evidence-url <url>	An evidence link to carry on the internal resolution comment (repeatable).

See also

• opschain docs cli/admin-jsm-requests-links — reading the recorded references back.
• opschain docs change-governance — the governance metadata block.