Bugs

Advance a bug's status one lifecycle stage at a time

Changed on Aug 28, 2026

Bearer atc:write (or cookie session); member+ write access. bunkai_transition_bug_status (migration 0054) enforces the lifecycle order open -> in_progress -> resolved -> closed: exactly one stage forward per call, never backward, never skipping a stage. Emits bug.status_changed with the previous status, new status, and current assignee.

post/api/v1/bugs/{id}/status

Request

Base URL: http://localhost:3000
URL: http://localhost:3000/api/v1/bugs/{id}/status
Auth: one of:
- API key in cookie sb-fmbpikzpkafptqximhxn-auth-token
- HTTP bearer

Path parameters

idstring uuid required

Request body

status'open' | 'in_progress' | 'resolved' | 'closed' required

Response

Bug status updated. Returns the updated Bug.

Changes

Aug 28, 20264528999528c6 Revision changes
- warning
  added the new test_outside_plan_project enum value to the / response property for the response status
- warning
  added the new test_outside_plan_project enum value to the / response property for the response status
- warning
  added the new test_outside_plan_project enum value to the / response property for the response status
- warning
  added the new test_outside_plan_project enum value to the / response property for the response status
- warning
  added the new test_outside_plan_project enum value to the / response property for the response status
Aug 27, 20262ca74ff5fec5 Revision changes
- info
  removed the test_outside_plan_project enum value from the / response property for the response status
- info
  removed the test_outside_plan_project enum value from the / response property for the response status
- info
  removed the test_outside_plan_project enum value from the / response property for the response status
- info
  removed the test_outside_plan_project enum value from the / response property for the response status
- info
  removed the test_outside_plan_project enum value from the / response property for the response status

Operation history