/bff/issue/bulk-status

Sets issue_status_id on every issue whose issue_key is in the list. Single UPDATE scoped to the caller organisation (through the project FK, plus originating_organisation_id for support tickets). The target status is validated once via assertStatusVisibleToOrganisation — a leaked id from another tenant is refused before the UPDATE runs.

IssuepostBffIssueBulk-status

Parameters

JSON body

Request body

application/json

issueKeysstring[]Required

Issue keys to update. Silently skips keys that do not belong to the caller organisation.

statusIdnumberRequired

Target status id. Must be visible to the caller organisation (system row or org-owned).

Response schema

1 status code documented

200Success

success"true"Required

matchednumberRequired

How many issues were actually updated.

requestednumberRequired

How many keys the caller submitted.

Response example

application/json

{
  "success": true,
  "matched": 0,
  "requested": 0
}

Request example

POST /bff/issue/bulk-status

post

curl -X POST "https://api.bizkithub.com/bff/issue/bulk-status" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
  "issueKeys": [
    "PROJ-123"
  ],
  "statusId": 0
}'

Need an API key?

All BizKitHub public API endpoints require authentication via API key.

Get API Key