/bff/issue/promote-comment-to-email

Takes an existing internal comment (channel = internal) and re-classifies it as an outbound customer reply (channel = email_out), then dispatches the same e-mail add-email would have sent (reporter + assignee, subject-threaded, org sender identity). The comment id is preserved so the timeline entry stays the same row instead of appearing as a duplicate. Fails when the comment is not internal, is spam-flagged, or does not belong to the given issue. Optionally accepts targetStatusId to apply a status change atomically before the e-mail is rendered.

IssuepostBffIssuePromote-comment-to-email

Parameters

JSON body

Request body

application/json

issueKeystringRequired

Issue key that owns the comment.

ExamplePROJ-123

commentIdstringRequired

Full wire-format comment id from IssueCommentItem.id — ${issueKey}_c${dbId}.

ExamplePROJ-123_c456

targetStatusIdnumberOptional

Optional status id to apply BEFORE the outbound e-mail is dispatched. Used when the operator promotes-and-closes in one click so the customer's e-mail carries the final status badge. Must be a system status or belong to the caller organisation.

Example4

Response schema

1 status code documented

200Success

successbooleanRequired

Whether the comment was promoted successfully.

commentIdstringRequired

Comment ID (unchanged from input).

ExamplePROJ-123_c456

Response example

application/json

{
  "success": false,
  "commentId": "PROJ-123_c456"
}

Request example

POST /bff/issue/promote-comment-to-email

post

curl -X POST "https://api.bizkithub.com/bff/issue/promote-comment-to-email" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
  "issueKey": "PROJ-123",
  "commentId": "PROJ-123_c456",
  "targetStatusId": 4
}'

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key