The Jira projects an issue can be created in
const url = 'https://beta-api.plune.ai/v1/bugs/jira/create/projects';const options = {method: 'GET', headers: {cookie: 'plune_session=<plune_session>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://beta-api.plune.ai/v1/bugs/jira/create/projects \ --cookie plune_session=<plune_session>The first step of «Create in Jira» (#1072): the first 100 projects, by key, that the account of the project’s connection has Create issues in - Jira’s GET /rest/api/3/project/search?action=create. The owner’s alone, by the session cookie alone, with a tier that has issue trackers, the Bugs section on and the connection working, refused as POST /v1/bugs/jira/find is. At most 60 calls a minute from you.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Header Parameters
Section titled “Header Parameters ”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.
Responses
Section titled “ Responses ”The projects
object
Where the account has the Create issues permission. project/search needs only read:jira-work, so an empty list is the account’s permissions, not the token’s scopes.
object
Jira has more than these first 100, by key.
Whether the token may write (write:jira-work). Always unknown: the connection keeps no scopes, and no documented call of Jira’s answers them - a token that cannot write is met at the create.
Example
{ "projects": [ { "id": "10000", "key": "ACME", "name": "Acme" } ], "more": false, "tokenWrites": "unknown"}No / invalid session — a CLI token is refused here, as on the routes of the Jira connection
object
Example
{ "error": "sign in required"}You are in the project as a reader, or not as its owner; or (only once the operator sets TIER_LIMITS_ENFORCE=true) a tier without the issue_trackers permission, answered in English then Ukrainian, naming the feature, with feature and tier
object
Example
{ "error": "project owner only"}The Bugs section is off in this project (code: bugs_disabled); or the project’s Jira connection is not working (code: jira_not_working, state one of rejected, ip_blocked, paused, no_token, error, none — none when it was never connected, no_token after a Disconnect, error when this server cannot read the saved token; paused is not met here, a tier that refuses Jira is the 403); Jira was not asked
object
Examples
The connection was disconnected
{ "error": "the project’s Jira connection is not working — its owner sees why in Settings → Integrations", "code": "jira_not_working", "state": "no_token"}The Bugs section is off
{ "error": "the Bugs section is off for this project: an owner turns it on in the project settings", "code": "bugs_disabled"}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
object
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"}The IP allowlist refused Plune
{ "error": "your company’s Jira accepts requests only from a list of addresses — add Plune’s address to it", "code": "jira_ip_blocked"}Jira asked Plune to slow down
{ "error": "Jira asked Plune to slow down — try again in 30 seconds", "code": "jira_rate_limited", "retryAfterSec": 30}Jira did not answer
{ "error": "Jira did not answer — try again in a few minutes", "code": "jira_unreachable"}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 Jira tokens under; Jira was not asked
object
Example
{ "error": "Jira is not configured on this server — contact your operator"}