opschain changes show
Included from Basic tier
opschain changes show <id|code> [--limit <n>] [--owner /|/projects/<code>] [--story-kinds <kind>,...]
Shows the record and its story: every run under it oldest first with
its status and how it joined (explicit, scope, inherited, linked),
its break-glass records, and the events of its runs, their steps and the
record's own ledger in order. Runs you cannot read are counted as withheld,
never named. -o json prints the same story as one document;
opschain changes export writes the whole story when it is longer than
--limit entries.
--story-kinds narrows the entries to the story kinds named —
record, approval, link, run, breakglass, attestation (the
mapping from event type to kind is in opschain docs resources/change_record) — as a comma list or by repeating the flag; the
runs and break-glass records are shown either way, and --limit counts
the matching entries. Without it every entry is shown; an unknown kind is
a usage error naming the kinds. opschain changes export always writes
the complete story.
opschain changes show CHG-2026-004 --story-kinds record,approval,link,breakglass,attestation
A record linked to an ITSM change (a JSM connection's change mapping —
opschain docs integrations-jsm) also shows the ITSM line: the
system, the change's id and page, its status as last applied, the state
the mapping projects it onto and whether the ITSM has approved it; the
last inbound move (the ITSM's event id and its own timestamp); and,
while work notes have not reached the ITSM, how many are waiting and the
warning naming why. The record links to the change; it never retypes the
CAB's decision.
ITSM: jsm CHG-12 via itsm — "Scheduled" (approved; approved by the ITSM)
https://limepoint.atlassian.net/browse/CHG-12
Last inbound move: changelog:20077 at 2026-11-19T10:00:00Z
Two more lines appear on a linked record when the ITSM moved it in a way
its three states cannot express. Held — the ITSM withdrew an approval
the record had: the header shows the state as approved (held) and the
line names the reason; no new run joins the record until the ITSM approves
it again, and the runs already under it continue. Pending close — the
ITSM closed the change while runs under the record were still running: the
line names the verdict, the ITSM's status and event, when it arrived and
how many runs were running; the record closes with that verdict when the
last run under it finishes, and a changes close in the meantime
supersedes it. -o json carries both as held and pending_close.
Change record CHG-2026-004 — upgrade the gateway (approved (held))
Held: no new run joins this record — approval withdrawn by jsm (CHG-12 moved to "Awaiting CAB"); runs already under it continue, and the ITSM's renewed approval lifts the hold
Pending close: completed — the ITSM closed the change ("Completed", event changelog:20090) at 2026-11-19T11:00:00Z while 2 run(s) ran; it applies when the last run under the record finishes (a close here supersedes it)
Flags
| Flag | Meaning |
|---|---|
--limit <n> | At most this many story entries (default 100). |
--owner <path> | The record's owner, / or /projects/<code> — narrows a code two owners hold; ignored for an id. |
--story-kinds <kind>,... | Only story entries of these kinds: record, approval, link, run, breakglass, attestation (comma list or repeatable; default every entry). |
Exit codes
| Code | Meaning |
|---|---|
| 0 | Shown. |
| 1 | Not found, or you may not read it. |
| 2 | Usage error. |