Skip to content
Plune Plune Plune Docs

Say something about this bug

POST
/v1/bugs/{id}/comments
 
curl --request POST \
  --url https://beta-api.plune.ai/v1/bugs/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/comments \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "body": "Reproduced on staging as well." }'

Plain text with its line breaks, trimmed, never empty, at most 8192 bytes; no edit. Audited on the bug as bug/comment, the text in the diff. Unlike a comment on a case, a suite or a run, a reader may NOT comment on a bug (403 read-only member, ADR 0057 question 4). Taken back with DELETE /v1/comments/{id}.

Authorizations

Section titled “Authorizations ”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters ”
id
required
string format: uuid

Header Parameters

Section titled “Header Parameters ”
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.

Request Body required

Section titled “Request Body required ”
Media type application/json
object
body
required

Trimmed; at most 8192 bytes (not characters) — the same cap the column enforces. Whitespace alone is refused.

string
>= 1 characters <= 8192 characters
Example 
{
  "body": "Reproduced on staging as well."
}

Responses

Section titled “ Responses ”

201

Section titled “201 ”

Written

Media type application/json

What somebody said about a case (B8-team T5): plain text with its line breaks, no Markdown, no edit — a changed mind is a second comment. The author is a userId; the dashboard names them from GET /v1/members.

object
id
required
string format: uuid
authorId
required
string
body
required
string
<= 8192 characters
createdAt
required
string format: date-time
Example 
{
  "id": "6f1c2b3a-0000-4000-8000-0000000000a4",
  "authorId": "6f1c2b3a-0000-4000-8000-0000000000a2",
  "body": "Step 3 is stale since the checkout redesign — the coupon field moved into the order summary."
}

400

Section titled “400 ”

Empty, or over the byte cap

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

401

Section titled “401 ”

No / invalid token or session

403

Section titled “403 ”

You are in the project as a reader

404

Section titled “404 ”

No such bug in this project

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

429

Section titled “429 ”

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"
}

Headers

Section titled “Headers ”
Retry-After
integer

Seconds until the window rolls over