Reorder Issue Types
POST/api/repairs/issue-types/reorder
Reorders and/or moves issue types in one call. Each row sets a type's parent and its position among its siblings. The whole call is refused (nothing changes) when a move would put a type under itself or make the tree more than 3 levels deep. Returns the full tree. Requires the Repairs: Settings permission.
repairs:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Fields:
items(array, required, 1–1000 rows)items.*.id(integer, required, distinct) — an existing issue type ID.items.*.parent_id(integer, optional, nullable) — the new parent;nullmakes it top-level.items.*.sort_order(integer, required, min 0) — the new position among its siblings.
Authentication: Bearer token with the repairs:write scope.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.