This module adds project and task fields to a Maintenance Plan, which will be automatically propagated to any maintenance request generated from a Plan.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Adds a project and a task to maintenance plans, so every maintenance request created from a plan is automatically linked to that project and task.
This module extends maintenance plans with two extra fields: a project and a task. Both appear on the maintenance plan form and list, right after the maintenance kind, and the task list is filtered to show only tasks belonging to the chosen project.
When a maintenance request is generated from a plan, the project and task set on the plan are copied onto the new request, so the maintenance work is automatically visible in the right project and task.
On the equipment form, the maintenance plans section now passes the equipment's project and default preventive task as defaults when a new plan is created from there, saving manual entry.
Business rules shown in the code: - The task field is computed from the project: changing the project clears the task, so you must pick a task again. - A project cannot be deleted while it is still used on a maintenance plan (deletion is restricted). - The task selection is limited to tasks of the selected project.
It touches the maintenance plan, maintenance equipment and maintenance request records, and links them to projects and tasks.
Depends on
Models and fields (2)
- maintenance.plan · extends an existing modeltask_id, project_id
- maintenance.equipment · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 14.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: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/maintenance.
terminal Installation and usage
No verified informationInstallation 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.