Custom Task Statuses
How to tailor task statuses to your workflow, reorder process stages, and understand how those changes appear in task cards and boards.
Custom task statuses let you adapt the workspace workflow to the real sequence of work. Instead of a generic process, the team can use terms that match its own work, such as “Bench verification,” “Flight code review,” or “Pre-launch calibration.”
In short: statuses are configured at the workspace level and immediately affect task cards, lists, filters, and Kanban. Base statuses cannot be removed, but their names can be overridden.
1. Where to configure statuses
Open the app menu and select Workspace → Task statuses. The section is available to the workspace owner because status changes affect the whole team and all projects.
2. What can be changed
- Status name. Both base and custom statuses can be renamed. This is useful when the team needs process-specific terms.
- Order of custom stages. Arrow buttons change how statuses are displayed in lists and Kanban.
- Custom statuses. Add status creates a new stage before the final status.
- Deletion. Only custom statuses can be removed. Base statuses stay part of the workflow.
After editing, tap Save. If you started making changes and want to return to the current saved state, use Reset.
3. How statuses appear in daily work
After saving, the updated names and order are used in task cards, filters, list mode, and Kanban. Before changing statuses, agree on the terms with the team: this becomes the shared vocabulary of the whole workspace.
4. Practical setup sequence
- Keep base statuses as process anchors.
- Add intermediate stages that the team actually uses.
- Arrange the stages in the order a task normally follows.
- Save the changes and check the main screen in list and Kanban modes.
What to read next
To see how statuses work with display modes, open Main Screen. If you need to split work by direction, configure projects. For the roles that can manage workspace settings, see Members and Roles.
Related topics
How to create projects in iTasks, manage their names, colors, and settings, and build a clear project structure inside a workspace.
Invitations to a workspace, team membership management, differences between OWNER, ADMIN, and MEMBER, and assigning project access.
Timezone, invite link, AI API, storage, members, JSON export, and workspace deletion.
How a workspace owner connects AI assistants to iTasks with a connection link, MCP URL, Bearer protection, and ready Codex CLI / Claude Code prompts.
FREE, PRO, and read-only mode, workspace limits, card payment in the website account or Telegram Stars in the app, and what happens after expiration.
Want to try this scenario in the app?
Open iTasks in Telegram now, and come back here when you need a full step-by-step guide.
Open iTasksExplore more features