OdooWiki OCA HUB

Project task parent completion blocking

project_task_parent_completion_blocking folder_open OCA/project open_in_new
Project Management License: AGPL-3

Prevents a task from being completed if a child task isn't completed.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Blocks closing a project task while it still has open subtasks, so parents can only be marked done once all their children are finished.

This module adds a single business rule to project tasks: a task cannot be moved into a closing stage if any of its subtasks is still open.

Where it appears: - On any project task form, when a user changes the task's stage to a stage that is marked as closing (a folded stage). - The rule also applies when the stage is changed from a list, kanban or any other view, because it is checked on the task itself.

What it does: - When the stage of a task changes, Odoo checks whether the new stage is a closing stage. - If it is, Odoo looks at all direct subtasks of that task. - If at least one subtask is not in a closing stage, the change is refused and an error message appears: "You can't close this task because it has open subtasks." - If all subtasks are already closed, the parent task can be closed normally.

What it touches: - It extends the existing project.task model only; no new fields, menus or reports are added. - It relies on the standard parent/subtask relationship and on the "closing stage" setting of project stages.

This helps teams keep parent tasks accurate: a parent task stays open until every child task is done.

Depends on

project
Models and fields (1)
  • project.task · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 18.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

No verified information

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.

info

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.