Skip to content

Create a Jira issue from a bug, and make the bug its mirror

POST
/v1/bugs/{id}/jira-create
curl --request POST \
--url https://beta-api.plune.ai/v1/bugs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/jira-create \
--header 'Content-Type: application/json' \
--cookie plune_session=<plune_session> \
--data '{ "project": "ACME", "issueType": "10001", "fields": { "priority": "2", "labels": [ "checkout" ] } }'

The last step (#1072, ADR 0057 §1). Reads the permissions and the screen again - nothing of what the dialog showed is taken - and checks every value against it (400, field by field), then POST /rest/api/3/issue: the summary and the description are the bug’s unless given, the description (and any textarea) Atlassian Document Format, ending with the bug’s marker. A required field Plune does not fill is the 422 jira_field_unsupported with fields and jiraUrl, before anything is sent; Jira refusing a value by a rule of its own is the 422 jira_create_refused with jiraUrl (what Jira wrote is never passed on). The bug then mirrors the issue (source jira, its key, id, site and link): its title, description and status are Jira’s from then on. Its files Plune keeps itself go to the issue, each in a request of its own under Jira’s limit (attachments). Once: the bug holds a claim while a try runs (no transaction is held across Jira’s calls) - a second try then is 409 jira_create_running. Once Jira answers with the issue’s key, the bug keeps it, so a try after a failure later on mirrors that issue (created: false) and never makes another. When Jira took the create but did not say what came of it (a 5xx, the network, an answer Plune cannot read, one without the key), it is 424 jira_create_unknown with jiraUrl: an issue may exist, so look for it in Jira; for 10 minutes another try is 409 jira_create_unknown, after that a try first searches the project for the bug’s marker (the end of the description, or a label when the screen has no description) and mirrors what it finds. Jira made the issue but the bug could not become its mirror (it went to the Bin, or another live bug mirrors that issue now): 409 jira_created_not_linked with the key and url; the bug keeps the key, so a try after a restore mirrors it. Audited on the bug (bug/event, createdInJira with the key), and - when the bug has files to count - a second entry after they are sent (sentToJira with the key, sent and notSent). The owner’s alone, by the session cookie alone, refused as POST /v1/bugs/jira/find is. At most 30 calls a minute from you.

id
required
string format: uuid
X-Plune-Project
string

Which of your projects to act in — an id from GET /v1/projects. Absent, your default project. A project you are not a member of answers 404, the same as one that does not exist. Ignored under a bearer token, which is bound to the project it was minted in.

Media type application/json
object
project
required

The key of the Jira project, any case.

string
<= 255 characters /^[A-Za-z][A-Za-z0-9_]*$/
issueType
required

The id of its issue type.

string
/^[0-9]{1,18}$/
fields

The values by field id, as JiraCreateField.type says - text (≤ 32767 characters), a number, or a list of ids or labels (≤ 100). summary and description left out are the bug’s.

object
key
additional properties
One of:
string
<= 32767 characters
attachments

The ids of the files to send, among prefill.attachments of the screen; left out - all of them; [] - none (and Create attachments is not asked). An id that is not one of them is the 400 jira_attachments_invalid.

Array<string>
<= 100 items
Example
{
"project": "ACME",
"issueType": "10001",
"fields": {
"priority": "2",
"labels": [
"checkout"
]
}
}

The bug, the mirror of the issue now

Media type application/json
object
bug
required
object
id
required
string format: uuid
key
required

The bug’s name for people (BUG-12): the project’s own number, handed out in order, never reused and never changed.

string
/^BUG-[0-9]+$/
number
required
integer
>= 1
source
required

Whose truth the row is. plune is a bug of the project’s own - a mirror the filter left and an owner adopted too (POST /v1/bugs/{id}/adopt), its Jira issue kept; jira mirrors an issue of the project’s Jira, made by POST /v1/bugs/jira/import (#1069): its title and description are Jira’s, brought up to date by each import, a PATCH of them or of state is 409 jira_field, and its streak never closes it - under after_n it tells «can be closed», as under manual (ADR 0057 §3).

string
Allowed values: plune jira github
title
required
string
>= 1 characters <= 200 characters
state
required
string
Allowed values: open closed
createdBy
required

The author’s user id, to be named from GET /v1/members; null when the account is gone.

string
nullable
caseCount
required

The live cases linked to the bug.

integer
commentCount
required
integer
evidenceCount
required

The evidence rows the bug holds (#2549). At 10 it is full: POST /v1/bugs/{id}/evidence is 409 evidence_limit.

integer
evidenceFileCount
required

The copies of pictures the bug’s evidence holds (#2549), against the 30 a bug keeps: 30 - evidenceFileCount more can be copied. A person’s own files (POST /v1/bugs/{id}/files) are not counted.

integer
createdAt
required
string format: date-time
updatedAt
required
string format: date-time
streak
required

«Passed X of N» (#1067, ADR 0057 §4). A linked case counts its green runs in a row while the bug is open - a mirror while Jira has not closed it (externalClosed, #2327): passed adds one, failed or broken resets, blocked, skipped and a muted result neither add nor reset; a run is one verdict, as the run itself counts the case - its latest result in each combination (a retry that passed is a pass), then the worst of the combinations; green counts once every combination of the run has a result, red at once (a failure in any combination); only a run newer than the one last counted and made after the case was linked counts, and with an environment in the rule only a run on it.

object
passed
required

The smallest streak among the live linked cases that are not muted (#2163); 0 with none.

integer
n
required

N of the project rule (bugs.close.n of the settings).

integer
>= 1 <= 5
canBeClosed
required

The bug is open (a mirror: externalClosed is not true, #2327), has a live case that is not muted, and every such case has N in a row - and nobody put it off for this series (POST /v1/bugs/{id}/wait, #2163). Under the rule after_n the bug then closes itself, unless flaky, a linked case is muted (isMuted of cases) or the bug mirrors a Jira issue (source jira, #1069), which it only tells.

boolean
flaky
required

A live linked case that is not muted is flaky: the streak is weak proof, and the rule after_n only tells, it does not close.

boolean
autoClosed
required

Closed by its streak (the rule after_n), not by a person (#1067). A person’s close or reopen sets it back to false.

boolean
reopenedByRegression
required

Open again because a linked case failed after its streak closed it - the list’s badge of a regression (#2163). A person’s move clears it.

boolean
externalKey
required

The key of the Jira issue the bug mirrors (ACME-123), as Jira last gave it (#1069). null on a bug of Plune’s own - as every external… field.

string
nullable
externalUrl
required

The issue in Jira: https://<site>/browse/<key>.

string
nullable
externalStatus
required

The name of the issue’s status in Jira at the last import.

string
nullable
externalStatusCategory
required

The key of that status’s category, as Jira gives it: new, indeterminate, done or undefined.

string
nullable <= 64 characters
externalClosed
required

externalStatusCategory is done: Jira counts the issue finished (ADR 0057 §3). The bug’s own state does not follow it; its streak does - a mirror Jira closed counts nothing, is not streak.canBeClosed, and a failure of its case tells bug.fails_again, as a bug of Plune’s closed by a person (#2327).

boolean
nullable
externalPriority
required

The name of the issue’s priority; null when it has none.

string
nullable <= 100 characters
externalAssignee
required

The name Jira shows for the assignee - never the e-mail; null when nobody is assigned.

string
nullable <= 200 characters
externalAttachments
required

The files of the issue as Jira names them, the first 100. Plune copies none (ADR 0072 §7).

Array
nullable <= 100 items
object
id
required
string
filename
required
string
size
required

Bytes, as Jira counts them.

integer
mimeType
required
string
nullable
url
required

Jira’s link to the file (content of its metadata) when it is on the site of the project’s connection, null otherwise. It opens in the person’s own Jira session: Plune does not fetch it.

string
nullable
externalUpdated
required

When the issue last changed in Jira, as the last import read it.

string format: date-time
nullable
externalSyncedAt
required

When Plune last read the issue into the bug.

string format: date-time
nullable
detachedAt
required

When the mirror was cut from its issue (ADR 0057 §11): its external… fields stay the last snapshot and no poll brings them up to date - but a left_filter mirror whose issue the filter brings again is attached again, and this is null once more. null on a mirror still attached and on a bug of Plune’s.

string format: date-time
nullable
detachedReason
required

Why it was cut, with detachedAt. left_filter (#1070): the daily full pass of the project’s poll by filter no longer found the issue in the filter. The bug is not deleted; once a pass finds the issue in the filter again, the mirror is attached again (both null).

string
nullable
Allowed values: ticket_missing connection_removed left_filter
jiraVia
required

Where a mirror came from (#1070): filter - the project’s poll by filter brought it; link - a person imported it by its link (POST /v1/bugs/jira/import), and that claim stays. Only a filter mirror is ever marked left_filter. null on a bug of Plune’s and on a mirror from before the poll whose origin is not known.

string
nullable
Allowed values: filter link
projectId
required
string
description
required

Markdown, at most 16384 bytes; shown by the safe component. null - none.

string
nullable
stateReason
required

Why the last move of state was made: manual, the words the person gave, or Plune’s own (#1067): automatically after N green runs in a row, regression after auto-close. null - never moved.

string
nullable
closedAt
required
string format: date-time
nullable
closedBy
required
string
nullable
cases
required

The live cases linked to the bug, by title.

Array<object>
object
id
required
string format: uuid
title
required
string
greenStreak
required

Green runs of the case in a row, counted while the bug is open - a mirror while Jira has not closed the issue (#2327); from 0 again after a reopen, by a person or by Jira (#1067).

integer
isFlaky
required
boolean
isMuted
required

Muted (#1246): left out of «every case has N»; while it is linked the rule after_n tells «can be closed» and does not close (#2163).

boolean
suiteId
required

The suite the case is in, for the path the card shows under its title (#2163); null - at the root.

string format: uuid
nullable
latestStatus
required

The status of the latest result of the case, read as a linked case of a requirement reads it - a muted failure is muted (#2163); null - no result yet.

string
nullable
Allowed values: passed failed broken blocked skipped muted
watchers
required

User ids of the people who are told about the bug: the author, and whoever pressed «watch».

Array<string>
watching
required

Whether the caller is one of them. The one field of the card that depends on who asks.

boolean
evidence
required

The failed results the bug was made from or added to, oldest first (#1066, ADR 0057 §6).

Array<object>
object
id
required
string format: uuid
resultId
required

The result, while it is there and its run is out of the Bin - a link that opens; null otherwise. The snapshot keeps the id.

string
nullable
runId
required

Its run, on the same terms.

string
nullable
resultState
required

present; deleted_by_cleanup - the plan’s cleanup of old history removed it (#1049); deleted - any other road (the Bin, a deleted case). Kept when the result goes: it cannot be read back after.

string
Allowed values: present deleted_by_cleanup deleted
snapshot
required

The result as it was when the evidence was taken, cleaned of credentials as every reader cleans it: result (status, raw status, source, sub-status, outcome, expected status, muted, case version, duration, params, when), errorContext (at most 16384 bytes; a longer one is cut and ends with …[truncated N bytes], and errorContextTruncated is true), failure (headline, steps, place, CI link - not the artifacts), steps (a person’s marks), case (id, title, keys, flaky and muted then), run (id, title, environment, started), takenBy, takenAt.

object
notCopied
required

The pictures named that were not copied, and why. The evidence is written all the same.

Array<object>
object
fileId
required
string
name
required

null when the id named no picture of the result.

string
nullable
reason
required

limit - over 10 a call or 30 a bug; budget - the bug’s copies in Plune’s storage would take more than half of the file budget; storage - the project’s bucket did not make the copy; missing - not a picture of that result (gone, a text, or never one).

string
Allowed values: limit budget storage missing
createdBy
required
string
nullable
createdAt
required
string format: date-time
files
required

The bug’s copies of the pictures of its evidence, oldest first. Read by GET /v1/files/{id} (one in the project’s bucket by GET /v1/files/{id}/link), by anyone who reads the bug; never deleted alone (DELETE /v1/files/{id} is a 409 evidence_file), they go with the bug.

Array<object>
object
id
required
string format: uuid
name
required
string
contentType
required
string
size
required
integer
storage
required

db: the bytes are GET /v1/files/{id}; bucket: a new object in a bucket, read by GET /v1/files/{id}/link — in the project’s bucket under a key of the bug’s, or (a built-in picture, #1428) in Plune’s own beside it.

string
Allowed values: db bucket
createdAt
required
string format: date-time
verifiedAt
required

A mirror marked verified in this series (#1071, Р319): when; null otherwise, and always on a bug of Plune’s.

string format: date-time
nullable
jiraWrite
required

What the write to Jira did for the last verification (#1071); null when none was asked.

object
cycle
required

The series verified: the event’s number, part of the comment’s marker.

integer
by
required

userId of who marked it verified.

string
at
required
string format: date-time
state
required
string
Allowed values: pending sent failed
sentAt
required

When the comment went to Jira.

string format: date-time
nullable
screenshots
required

The screenshots of the passing results attached.

integer
missing
required

The pictures of the passing results not attached: gone, over 2 MiB or over Jira’s upload limit, in a bucket (the project’s or Plune’s own) that could not be reached or read whole then, or past the 60 a comment carries.

integer
attached
required

The result files already attached to the issue for this verification: a try after a stop between two sends only the rest.

Array<string>
transition
required

null: no transition in the table.

object
name
required
string
made
required
boolean
reason
required
string
nullable
Allowed values: no_transition fields_required no_permission refused
error
required
string
nullable
Allowed values: rejected ip_blocked busy unreachable forbidden unavailable not_working paused
streakMove
required

What the streak last did, while it is the last move of the state; null after a person’s move, or when the streak never moved it (#2163).

object
kind
required
string
Allowed values: auto_closed regression
at
required
string format: date-time
run
required

The run of the move; null once it is in the Bin or gone.

object
id
required
string
title
required
string
nullable
environment
required

The environment of that run, as it was then.

string
nullable
case
required

The case that failed - a regression’s; null on a close, or once the case is in the Bin or gone.

object
id
required
string format: uuid
title
required
string
created
required

false - an earlier try had made the issue (its key kept, or found by the marker), and mirrored: not made twice.

boolean
synced
required

false - Jira made the issue but did not give it back: the mirror is built from the key and id Jira answered with and the bug’s own title and description, its status empty, until an import of the issue, or a poll whose filter brings it, fills them.

boolean
attachments
required

The bug’s files sent to the issue, and those that were not: over Jira’s upload limit or 2 MiB, in a bucket that could not be reached or read whole then, or refused. Not tried again. A file left out of attachments is in neither.

object
sent
required
integer
notSent
required
integer
Example
{
"bug": {
"id": "7b3e1d2c-0000-4000-8000-00000000e069",
"key": "BUG-13",
"number": 13,
"source": "jira",
"title": "Checkout total ignores the coupon",
"state": "open",
"createdBy": "6f1c2b3a-0000-4000-8000-0000000000a2",
"caseCount": 0,
"commentCount": 0,
"evidenceCount": 0,
"evidenceFileCount": 0,
"createdAt": "2026-09-16T09:12:04.151Z",
"updatedAt": "2026-09-16T09:12:04.151Z",
"streak": {
"passed": 0,
"n": 3,
"canBeClosed": false,
"flaky": false
},
"autoClosed": false,
"reopenedByRegression": false,
"externalKey": "ACME-124",
"externalUrl": "https://acme.atlassian.net/browse/ACME-124",
"externalStatus": "To Do",
"externalStatusCategory": "new",
"externalClosed": false,
"externalPriority": "High",
"externalAssignee": "John Doe",
"externalAttachments": [
{
"id": "10001",
"filename": "screen.png",
"size": 219136,
"mimeType": "image/png",
"url": "https://acme.atlassian.net/rest/api/3/attachment/content/10001"
},
{
"id": "10002",
"filename": "checkout.log",
"size": 4096,
"mimeType": "text/plain",
"url": "https://acme.atlassian.net/rest/api/3/attachment/content/10002"
}
],
"externalUpdated": "2026-10-31T10:05:00.000Z",
"externalSyncedAt": "2026-09-16T09:12:04.151Z",
"detachedAt": null,
"detachedReason": null,
"jiraVia": "link",
"projectId": "u-shop::default",
"description": "Apply SAVE10, then pay: the total is the full price.",
"stateReason": null,
"closedAt": null,
"closedBy": null,
"cases": [],
"watchers": [
"6f1c2b3a-0000-4000-8000-0000000000a2"
],
"watching": true,
"evidence": [],
"files": [],
"streakMove": null,
"verifiedAt": null,
"jiraWrite": null
},
"created": true,
"synced": true,
"attachments": {
"sent": 0,
"notSent": 0
}
}

Invalid body, a value the screen does not take (validation failed — fields.<id>: …), or attachments naming a file that is not one the create can send (jira_attachments_invalid, with those ids in attachments); Jira was not asked to create

Media type application/json
object
error
required
string
Example
{
"error": "not among the bug’s files Plune can send to Jira — pick from the files the dialog lists",
"code": "jira_attachments_invalid",
"attachments": [
"7b3e1d2c-0000-4000-8000-0000000000f1"
]
}

No / invalid session — a CLI token is refused here, as on the routes of the Jira connection

Media type application/json
object
error
required
string
Example
{
"error": "sign in required"
}

You are in the project as a reader, or not as its owner; a tier without issue_trackers (with TIER_LIMITS_ENFORCE=true); or the account of the connection lacks a permission Jira asks of the create in that project (code: jira_no_permission, with missing - of BROWSE_PROJECTS, CREATE_ISSUES, CREATE_ATTACHMENTS; CREATE_ATTACHMENTS only for a bug with files), as mypermissions with the project key says it

Media type application/json
object
error
required
string
Example
{
"error": "the account of the connection may not CREATE_ISSUES in Jira project ACME",
"code": "jira_no_permission",
"missing": [
"CREATE_ISSUES"
]
}

Jira does not give the project or its issue type - it does not exist, or the account may not create there (jira_project_unavailable, with project); the bug is not one of the project’s live bugs; or the project of X-Plune-Project is not one of yours

Media type application/json
object
error
required
string
Example
{
"error": "Jira did not give project NOPE or its issue type: it does not exist, or the account of the connection may not create issues there",
"code": "jira_project_unavailable",
"project": "NOPE"
}

not_plune (a mirror already), not_open, jira_create_running (another try of this bug is running), jira_create_unknown (an earlier try may have made an issue - look in Jira; with jiraUrl), jira_created_not_linked (Jira made the issue, with key and url, but the bug went to the Bin or another live bug mirrors it); or, as for the import, bugs_disabled and jira_not_working

Media type application/json
object
error
required
string
Example generated
{
"error": "example"
}

Jira requires fields Plune does not fill (jira_field_unsupported, with fields and jiraUrl), or refused the issue (jira_create_refused, with jiraUrl): create it in Jira

Media type application/json
object
error
required
string
Example
{
"error": "Jira requires fields Plune does not fill (Security Level) — create the issue in Jira",
"code": "jira_field_unsupported",
"fields": [
{
"id": "security",
"name": "Security Level",
"type": "securitylevel"
}
],
"jiraUrl": "https://acme.atlassian.net/browse/ACME"
}

Jira did not give the issue for a reason of its own; what Jira wrote is never passed on. jira_token_rejected — a 401: the connection becomes rejected and its token is not sent again until the owner connects anew; jira_ip_blocked — Jira’s IP allowlist refused Plune: the connection becomes ip_blocked; jira_rate_limited — a 429, with retryAfterSec (Jira’s Retry-After, else 30); jira_unreachable — a 5xx, the network, the 15 s deadline, a redirect, an answer over 1 MB or one Plune cannot read. A 424 and not a 502/504: a proxy replaces the body of those. And jira_create_unknown (with jiraUrl): Jira took the create and did not say what came of it - an issue may exist, look for it in Jira before trying again

Media type application/json
object
error
required
string
Examples

Jira rejected the token

{
"error": "Jira rejected the token of the project’s connection — its owner connects it again with a new token",
"code": "jira_token_rejected"
}

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.

Media type application/json
object
error
required
string
Example generated
{
"error": "example"
}
Retry-After
integer

Seconds until the window rolls over

The server has no key to keep Jira tokens under; Jira was not asked

Media type application/json
object
error
required
string
Example
{
"error": "Jira is not configured on this server — contact your operator"
}