Delete a comment from a project release. A successful delete returns 204 with an empty body.
Deleting needs edit access to the release, and returns 403 without it. The API doesn't check who wrote the comment, so anyone who can edit the release can delete any of its comments.
Delete a project release comment
Delete a comment from a project release. A successful delete returns
204with an empty body.Deleting needs edit access to the release, and returns
403without it. The API doesn't check who wrote the comment, so anyone who can edit the release can delete any of its comments.Path Parameters
slug:requiredstringThe workspace slug. It appears in your Plane URLs. In
https://app.plane.so/my-team/projects/, the slug ismy-team.project_id:requiredstringThe project the release belongs to. Accepts the project UUID or its bare identifier, for example
ENG.release_id:requiredstring (uuid)The release the comment is on.
pk:requiredstring (uuid)The id of the comment to delete.
Response shaping
fields:optionalstringComma-separated list of fields to return. A successful delete has no body, so this has no visible effect. See Sparse fields.
Requestable here:
comment_html,comment_id,created_at,created_by_id,edited_at,id,is_hidden,is_resolved,parent_id,release_id,updated_at,updated_by_id.Scopes
releases.comments:writeErrors
400invalid_request401unauthorized402payment_required403forbidden404not_found406not_acceptableAcceptheader asks for a representation the API can't produce.409conflict413payload_too_large415unsupported_media_typeContent-Typeisn't one this endpoint accepts.429rate_limitedRetry-Afterheader before retrying.No response body.