Set what Plune writes to Jira when a mirror is verified
const url = 'https://beta-api.plune.ai/v1/projects/example/integrations/jira/write';const options = { method: 'PUT', headers: { cookie: 'plune_session=<plune_session>', 'Content-Type': 'application/json' }, body: '{"sampleIssue":"ACME-123","verified":{"id":"31","name":"Close issue","toId":"10002","toName":"Done"}}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request PUT \ --url https://beta-api.plune.ai/v1/projects/example/integrations/jira/write \ --header 'Content-Type: application/json' \ --cookie plune_session=<plune_session> \ --data '{ "sampleIssue": "ACME-123", "verified": { "id": "31", "name": "Close issue", "toId": "10002", "toName": "Done" } }'Owner only (#1071, ADR 0072 §1, §6; Р320, Р325). The event → transition table, whole: the sample issue and the transition «verified» makes, or null for a comment only. Before anything is kept Jira is asked mypermissions for the sample issue: the account must hold ADD_COMMENTS, CREATE_ATTACHMENTS and TRANSITION_ISSUES there (422 jira_no_permission with missing). When a person marks a mirror verified (POST /v1/bugs/{id}/verify), Plune writes a comment - the cases, how many runs in a row passed, when in UTC, the environment, a link to the run - with the screenshots of the passing results, and makes the transition when the bug’s issue offers it. Recorded in the audit feed as a jira_connection update. Needs a working connection and a tier with issue trackers. Session cookie only. The permissions: ADD_COMMENTS, CREATE_ATTACHMENTS, TRANSITION_ISSUES.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”An id from GET /v1/projects
Request Body required
Section titled “Request Body required ”object
The key of any issue of the Jira project, as KAN-1; its project is where the write permissions are checked.
object
Example
{ "sampleIssue": "ACME-123", "verified": { "id": "31", "name": "Close issue", "toId": "10002", "toName": "Done" }}Responses
Section titled “ Responses ”Set — the same body as GET
object
null when no Jira was ever connected.
object
working; rejected — Jira answered 401: a new token is needed, and Plune does not send this one again; ip_blocked — Jira’s IP allowlist refused Plune; error — another failure, stateReason says which; paused — the project’s tier does not include issue trackers (Free, an expired tier or one switched off) while the operator enforces the tier limits: nothing is asked of Jira and nothing is lost; no_token — disconnected: the settings stay, a token connects it again (a disconnected connection reads no_token, never paused).
The code of the last failure when state is rejected, ip_blocked or error; null otherwise.
When the saved connection was last checked: the save itself, or POST …/test.
When Jira last answered a read — what Plune holds of Jira is as of this time.
userId of the owner who connected it, or last changed it.
userId of the owner who disconnected it; null while connected.
Owner only: the e-mail of the Atlassian account.
The poll by filter (#1070) as a member reads it.
object
When the next pass is due; null while the poll is off.
A pass runs now (it holds the lease). While it does, nextPollAt is a watchdog for a lost pass, not the next poll: the pass sets that when it ends.
The start of the last pass that read to the end: the next asks Jira for what changed since 10 minutes before it.
null until the first pass, and after the filter changed.
object
Issues that wrote nothing: their mirror keeps the same updated, it is detached for a reason other than left_filter, or a bug adopted into Plune holds the issue - it is not mirrored again (decision of 12.11.2026).
null — read to the end, or to its cap of issues (the next pass goes on from there a minute later). rejected / ip_blocked — Jira answered 401 / its IP allowlist refused Plune: the connection takes that state and polling stops. busy — Jira answered 429: the pass is tried again after its Retry-After at the least (retryAt), four tries in all; unreachable — a 5xx, the network, a redirect: the same tries. filter_unavailable — the saved filter is gone, or the account may not see it; filter_invalid — Jira refused the JQL; too_large — a page of the search is over 1 MB; bugs_disabled — the project’s Bugs section is off; bugs_quota — the project holds as many bugs as its plan allows; token_unreadable — this server’s key does not open the saved token. All but the first two are tried again at the next poll.
When a busy or unreachable pass is tried again; null otherwise.
The start of the last full pass (ADR 0072 §3): the whole filter read, not only what changed, and every mirror of the site the filter no longer holds detached with left_filter. The next one is due 24 h later; absent until the first.
The left_filter mirrors this pass attached again: their issue is in the filter again - any pass that brings it, the full one or the window. Absent on an outcome from before the re-attach.
The mirrors this pass detached as left_filter - only a full pass does. Absent on an outcome from before the full pass.
Only when a full pass that read to the end detached nothing by its safety valve: empty - the filter held no issue; too_many - more than half of the site’s filter mirrors, and 5 or more, would have gone at once (fewer than 5 are detached). mirrors: the site’s live mirrors the filter brought; missing: those the pass did not find. Nothing is detached until a full pass finds the filter as it should be.
object
The event → transition table (#1071, Р325): the issue its transitions were read from, and the transition «verified» makes - null, a comment only.
object
object
The addresses Plune calls Jira from, for a Jira that takes requests from an allowlist only (ADR 0072 §9). A change of them is announced 14 days ahead. Empty when the server names none.
true exactly when PUT would be refused now for the tier (403, issue_trackers: TIER_LIMITS_ENFORCE=true and a tier without issue trackers — Free, an expired tier or one switched off); worked out as paused is. Unlike paused it says so with nothing connected and after Disconnect. Always false in report mode.
Example
{ "connection": { "site": "acme.atlassian.net", "tokenKind": "scoped", "state": "working", "stateReason": null, "checkedAt": "2026-09-16T09:12:04.151Z", "lastReadAt": "2026-09-16T09:12:04.151Z", "connectedBy": "u-shop", "connectedAt": "2026-09-16T09:12:04.151Z", "disconnectedBy": null, "disconnectedAt": null, "email": "user@plune.ai", "poll": { "enabled": true, "filterId": "10010", "jql": null, "intervalMinutes": 15, "nextPollAt": "2026-10-29T09:15:00.000Z", "running": false, "lastPolledAt": "2026-09-16T09:12:04.151Z", "last": { "startedAt": "2026-09-16T09:12:04.151Z", "finishedAt": "2026-09-16T09:12:04.151Z", "created": 2, "updated": 1, "unchanged": 4, "error": null, "retryAt": null, "fullPassAt": "2026-09-16T09:12:04.151Z", "reattached": 0, "detached": 0 } }, "write": { "sampleIssue": "ACME-123", "verified": { "id": "31", "name": "Close issue", "toId": "10002", "toName": "Done" } } }, "outboundAddresses": [ "203.0.113.7" ], "paidOnly": false}Invalid body
object
Example generated
{ "error": "example"}No / invalid session — a CLI token is refused here
You are in the project, but not as its owner; or (with TIER_LIMITS_ENFORCE=true) a tier without the issue_trackers permission
object
Example generated
{ "error": "example"}No such project among yours, no Jira was ever connected, or Jira does not give the sample issue (jira_issue_unavailable)
object
Example
{ "error": "Jira did not give issue KAN-9: it does not exist, or the account of the connection may not see it", "code": "jira_issue_unavailable", "key": "KAN-9"}The connection is not working (jira_not_working, with its state)
object
Example generated
{ "error": "example"}The account of the connection lacks a write permission in the sample issue’s project (jira_no_permission); nothing was saved
object
Example
{ "error": "the account of the connection may not TRANSITION_ISSUES in the project of ACME-123", "code": "jira_no_permission", "missing": [ "TRANSITION_ISSUES" ]}Jira rejected the token (jira_token_rejected, the connection becomes rejected), refused Plune’s address (jira_ip_blocked), asked to slow down (jira_rate_limited) or did not answer (jira_unreachable)
object
Example generated
{ "error": "example"}Rate-limited: the per-route throttle, or the per-minute request limit of the plan an API token counts by (#1442; the body names the plan, #2092). Retry-After carries the seconds until the window rolls over.
object
Example generated
{ "error": "example"}Headers
Section titled “Headers ”Seconds until the window rolls over
The server has no key to keep tokens under
object
Example
{ "error": "Jira is not configured on this server — contact your operator"}