[16.0][ADD] project_state_extend: add new module

[kaynnan]

Add project_state_extend module to allow custom project states beyond Odoo's native ones.

Technical Details

• New model project.state.extend for state management
• ES6 service to load states from database
• Patches native Odoo widgets to include custom states

Demo States Included

• Pending Review, Awaiting Approval, In Progress, Blocked, Completed

cc @marcelsavegnago @WesleyOliveira98 @CristianoMafraJunior

[CristianoMafraJunior]

LGTM

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[alexey-pelykh]

Thanks for the contribution @kaynnan. The idea of extending project states is useful, but there are several issues that need to be addressed.

Wrong native color values

In both project_project.py and project_update.py, the hardcoded color dicts have incorrect values compared to Odoo's actual STATUS_COLOR:

Status	Your value	Odoo native
on_track	10	20
off_track	1	23

Also missing False: 0 fallback. Import and reuse STATUS_COLOR from odoo.addons.project.models.project_update rather than re-declaring.

Duplicated logic

_get_extended_status_selection() and _compute_*_color() are copy-pasted between project_project.py and project_update.py with minor differences. Factor into a shared helper.

/* eslint-disable */ blanket

The JS file has a blanket eslint disable. Use targeted directives instead.

No validation on technical_name

No @api.constrains to enforce lowercase, no-spaces, and no collision with native state keys (on_track, at_risk, off_track, on_hold, to_define). A user creating technical_name = "on_track" would shadow the native state.

Data integrity on delete

If a custom state is deleted while still assigned to projects/updates, those records will have invalid last_update_status/status values. Consider preventing deletion of in-use states.

Documentation mentions Tasks but module doesn't extend tasks

USAGE.rst says "Projects and Tasks" but the module only extends project.project and project.update.

Happy to re-review once addressed.

[alexey-pelykh]

Thanks @kaynnan — excellent work addressing all the feedback. Re-reviewing after the update:

1. Wrong native color values — ✅ Now imports STATUS_COLOR from odoo.addons.project.models.project_update via status_utils.py. No more hardcoded values.

2. Duplicated logic — ✅ Factored into shared get_extended_status_selection() and get_extended_status_color() in status_utils.py.

3. Blanket eslint-disable — ✅ Removed. Clean JS with proper OWL patches.

4. No validation on technical_name — ✅ @api.constrains with regex ^[a-z][a-z0-9_]*$ + collision check against NATIVE_STATUS_KEYS + SQL unique constraint.

5. Data integrity on delete — ✅ unlink() override checks projects and updates before allowing deletion.

6. Documentation scope — ✅ USAGE.rst now correctly scoped to Projects only.

All CI green. Well done on the thorough rework.

Co-Reviewed-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[marcelsavegnago]

LGTM

[leemannd]

/ocabot merge nobump

[OCA-git-bot]

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 16.0-ocabot-merge-pr-1586-by-leemannd-bump-nobump, awaiting test results.

[OCA-git-bot]

@leemannd your merge command was aborted due to failed check(s), which you can inspect on this commit of 16.0-ocabot-merge-pr-1586-by-leemannd-bump-nobump.

After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red.

[leemannd]

There are errors while trying to merge @kaynnan , could you have a look at them?