This module adds a server action that allows to duplicate a task with its child tasks.
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a "Duplicate with subtasks" action on tasks that copies a task together with all of its child subtasks, at any depth.
This module adds a server action called "Duplicate with subtasks" on the task model project.task. It appears in the Action menu (the cog/action dropdown) available on tasks, so users can select one or several tasks and choose it to duplicate them.
When used, the selected task is copied and every child subtask is copied as well, recursively, so grandchildren and deeper levels are also duplicated. Each copied subtask is re-attached to the copy of its parent, keeping the same task hierarchy.
After the duplication: - If only one task was duplicated, Odoo opens the new task in a form view directly in edit mode. - If several tasks were duplicated, Odoo shows a list view filtered to only the newly created tasks.
No new fields, menus, reports, emails or scheduled jobs are added. The module only extends the existing project.task model with the duplication behaviour and registers the server action that triggers it.
Depends on
Models and fields (1)
- project.task · extends an existing model
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: 4 confirmed, 5 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.0Usage
Source · Odoo 16.0To use this module, there are two ways:
- Go to a task: Action > Duplicate with subtasks.
- Go to the tasks list view, select the tasks you want to duplicate: Action > Duplicate with subtasks.
No verified information in OCA: Installation, Configuration.
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.