opschain admin jsm-requests links

integrations:jira-service-management

Lists the jsm:request / jira:issue typed external references recorded on governance metadata blocks, joined to the governed subject carrying each one — the answer to "which OpsChain changes carry this ticket". Authorisation is per row: only links whose subject target you may read are served.

opschain admin jsm-requests links --request SUP-123
REQUEST  SYSTEM  RELATIONSHIP  RUN       KIND    TARGET
SUP-123  jsm     resolves      0193…     change  /projects/demo/environments/prod

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).
--request <key>	Keep only links to this request key, e.g. SUP-123.
--system <name>	Keep only links of this system: jsm or jira (default: both).
--filter <column>[!]=<value>	Keep only rows matching the term (repeatable; terms AND). Columns are the printed table headers lowercased; * wildcards match the whole cell case-insensitively, != negates, commas mean any-of. Applied client-side. Grammar: opschain docs cli.

See also

• opschain docs cli/approvals-set-metadata — how references land on a subject.