This module extends Odoo's project state selection widget to allow adding extended state options beyond the standard ones (On Track, At Risk, Off Track, On Hold).
Custom states can be configured with:
- Display name (translatable)
- Technical name (unique identifier)
- Color (0-11 for status bubble display)
- Sequence (ordering in selection lists)
Custom states are available for Projects through the same state selection widget used by native Odoo.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Lets you create your own project statuses (beyond On Track, At Risk, Off Track, On Hold) with a name, color and order, and use them on projects and project updates.
This module adds a new configuration screen where you can define extra project statuses. Each status has a display name, a technical name (lowercase, unique, cannot reuse the standard status names), a color index from 0 to 11 for the status bubble, and a sequence number that controls the order in the dropdown lists. You can also archive statuses you no longer use.
Once created, the custom statuses appear in the status selection of projects and of project updates, next to the standard ones. The status bubble and the kanban progress bar use the color you chose. The status of a project update is tracked in the chatter.
Business rules: the technical name must start with a letter and contain only lowercase letters, numbers and underscores; it must be unique; and it cannot be one of the standard status names. A status that is still used by at least one project or one project update cannot be deleted.
Where it appears: a new menu "Custom States" under Project > Configuration, with a list and a form view, plus a search view with an Archived filter. Regular users can read the statuses; only project managers can create, edit or delete them. The module touches project.project, project.update and the new project.state.extend model.
Depends on
Menus it adds
Models and fields (3)
- project.update · extends an existing modelstatus
- project.project · extends an existing modellast_update_status
- project.state.extend · new modelname, color (Color Index), active, sequence, technical_name
Text generated by AI (DeepSeek) from reading the Odoo 16.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.0 of OCA/project.
terminal Installation and usage
OCA documentation · Odoo 16.0Configuration
Source · Odoo 16.0To configure custom project states:
- Go to Project > Configuration > Extended States
- Click Create
- Fill in the form:
- Name: Display name for the state (e.g., "Pending Review")
- Technical Name: Unique identifier (lowercase, no spaces, e.g., "pending_review")
- Color: Select a color index from 0 to 11 for the status bubble
- Sequence: Lower numbers appear first in selection lists
- Active: Uncheck to archive the state
- Click Save
The extended state will now be available in the state selection widget for Projects.
Note: Technical names must be unique across all extended states.
Usage
Source · Odoo 16.0After configuring extended states, you can use them in Projects:
For Projects:
- Open a project
- Below the standard "Status" field, you'll see the "Custom State" field
- Click to select from available extended states
- The selection will save automatically
The extended state field uses the same widget as the native status field, providing a consistent user experience with colored status bubbles.
Kanban View:
Custom states are also visible in Kanban views for Projects, with the configured color displayed as a status bubble.
No verified information in OCA: Installation.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.