Retrieves a single status schema definition by its unique identifier, returning the complete workflow configuration including available status steps, allowed transitions between statuses, and validation rules. Status schemas define the lifecycle states and workflow logic for tasks and requests within a space, controlling which status changes are permitted and how work items progress through their lifecycle. Use this endpoint when you need to display available statuses in a dropdown, validate status transition requests before submission, render workflow diagrams showing state transitions, or understand the complete status model for a space. The returned StatusSchema object contains the schema name, creator information, array of status step definitions, and transition matrix defining valid status changes. Essential for building task management interfaces, workflow automation tools, and status validation logic. For example, call this endpoint when loading a task editing form to populate the status dropdown with only valid next statuses based on the current task state, or when implementing workflow visualization showing all possible paths through the status lifecycle. The schema is typically configured per space and can vary between workspaces to support different team workflows and processes.
Key Features:
-
Returns complete status schema with all workflow steps and transition rules
-
Includes status names, IDs, and metadata for each workflow state
-
Provides transition matrix showing valid status change paths
-
Supports validation of status updates before submitting changes
Authorization Logic:
-
Requires view or manage permissions for the space
-
Any user with space access can retrieve status schemas for workflow understanding
-
Status schema visibility follows space permission boundaries
Usage Example:
When rendering a task detail page, call GET /v2/spaces/w5PmrE9p0kicqqRSVJ3VBQ/statusschema/statusSchema123 to retrieve the workflow definition. Use the steps array to populate the status selector with available states like Not Started, In Progress, Blocked, and Completed. Reference the transitions array to determine which status changes are allowed from the task's current status, enabling or disabling transition buttons accordingly.