opschain admin jsm-connections
integrations:jira-service-management
Manage the Jira Service Management connections the JSM integration
writes through. A connection registers one site — an Atlassian cloud
site (https://yoursite.atlassian.net) or a Jira Data Center base
URL — and optionally scopes writes to named project keys: a write
to a request outside the scoped projects refuses by name.
Authentication follows the site kind: supply --auth-email and an API
token for Atlassian cloud (basic authentication as that account), or
omit the email and supply a Data Center personal access token, sent as
a bearer.
The custody posture is reference-first: the record stores
api_token_ref, a secret-vault:// address, never the token itself.
Supply a reference with --api-token-ref — it is resolved when it is
set, so a record can never point at a reference that does not resolve —
or supply the token via --api-token-env or --api-token-prompt
(never on the command line) and the server stores it in the platform
vault under jsm-connections/<code>/credential and pins that reference
for you. No read, audit row or error ever returns token material.
Creating or enabling a connection requires the
integrations:jira-service-management entitlement. On licence lapse
stored connections are retained and only new registrations, enabling
writes and outbound request writes refuse — everything lights back up
on upgrade.
| Subcommand | Purpose |
|---|---|
list | Every connection: site, project scope, enabled state, health. |
show <code-or-id> | One connection's record. |
create <code> | Register a connection (reference pinned, or inline token vaulted). |
update <code-or-id> | Change fields; a supplied token or reference re-pins. |
delete <code-or-id> | Remove a connection. |
test <code-or-id> | Validate the record without calling JSM. |
provision-webhook <code-or-id> | Provision Jira webhook ingestion on the signed inbound lane (/api/hooks/jsm-<code>). |
Every verb rides the v2 JsmIntegrationService; the server requires an
updatable determination on /admin/integrations/jsm/connections (a
plain /admin rule covers it by prefix). Exit codes: 0 on success, 1
when a call fails or the token is rejected, 2 for usage errors.
See also
opschain docs integrations-jsm— the whole integration.opschain docs cli/admin-jsm-requests— working requests through the write door.