This module recomputes forecast end date of project.task, based on deadline date of project.task.
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Adds a forecast end date on project tasks that is automatically filled from the task deadline, so the forecast planning shows when work is expected to finish.
This module extends project tasks with an extra date field used by the project forecast planning feature.
- On every task, a new "forecast planned end" date is calculated automatically from the task's deadline date. When you change the deadline, the forecast end date follows it.
- The field is stored and can also be edited manually, so users are not forced to accept the value coming from the deadline.
- The calculation is triggered only by the deadline field, so other task changes do not alter the forecast end date.
- It works together with the project forecast line module, which is required for this module to be installed.
Where it appears: on project task records, in the forecast-related date fields of the task form. No new menus, buttons, reports, emails or scheduled actions are added by this module.
Business rule added: the planned end of a task in the forecast is kept in line with the deadline the user sets, reducing manual double entry and keeping planning dates consistent. The module touches the project.task model only.
Depends on
Required by other modules
Models and fields (1)
- project.task · extends an existing modelforecast_date_planned_end
Text generated by AI (DeepSeek) from reading the Odoo 15.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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/project.
terminal Installation and usage
OCA documentation · Odoo 15.0Usage
Source · Odoo 15.0Install the module.
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.