Skip to Content
Odoo model · Enterprise

project.timesheet.forecast.report.analysis

Planning & Timesheets Analysis. Defined in module project_timesheet_forecast; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 2 fields added, 1 removed, 0 renamed, 2 type changes.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 project_timesheet_forecast
  4. Odoo 19 project_timesheet_forecast
  5. Odoo 20 project_timesheet_forecast

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 17 to 18

Community only All changes in this step

Not covered: this step compares Community modules only and this model belongs to an Enterprise module.

Odoo 18 to 19

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

Odoo 19 to 20

Community + Enterprise All changes in this step

Fields removed (1)

FieldTypeModuleNotes
user_idmany2oneproject_timesheet_forecast

Fields added (2)

FieldTypeModule
currency_idmany2oneproject_timesheet_forecast
task_idmany2oneproject_timesheet_forecast

Type changed (2)

FieldOdoo 19Odoo 20
effective_costs floatmonetary
planned_costs floatmonetary

All fields declared on project.timesheet.forecast.report.analysis (22)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 22 fields
FieldTypeLabelModule1617181920
company_idmany2one res.companyCompanyproject_timesheet_forecastE
currency_idmany2oneCurrencyproject_timesheet_forecastE
differencefloatTime Variance(Planned - Actual)project_timesheet_forecastE
effective_billable_hoursfloatActual Billable Timeproject_timesheet_forecast_saleE
effective_costsmonetaryActual Costsproject_timesheet_forecastE
effective_hoursfloatActual Timeproject_timesheet_forecastE
effective_marginfloatActual Marginproject_timesheet_forecast_saleE
effective_non_billable_hoursfloatActual Non-Billable Timeproject_timesheet_forecast_saleE
effective_revenuesfloatActual Revenuesproject_timesheet_forecast_saleE
employee_idmany2one hr.employeeEmployeeproject_timesheet_forecastE
entry_datedateDateproject_timesheet_forecastE
is_publishedbooleanproject_timesheet_forecastE
line_typeselectionTypeproject_timesheet_forecastE
planned_billable_hoursfloatPlanned Billable Timeproject_timesheet_forecast_saleE
planned_costsmonetaryPlanned Costsproject_timesheet_forecastE
planned_hoursfloatPlanned Timeproject_timesheet_forecastE
planned_marginfloatPlanned Marginproject_timesheet_forecast_saleE
planned_non_billable_hoursfloatPlanned Non-Billable Timeproject_timesheet_forecast_saleE
planned_revenuesfloatPlanned Revenueproject_timesheet_forecast_saleE
project_idmany2one project.projectProjectproject_timesheet_forecastE
task_idmany2one project.taskTaskproject_timesheet_forecastE
user_idmany2one res.usersAssigned toproject_timesheet_forecastE

Related models

Linked by its relational fields: hr.employeeproject.projectproject.taskres.companyres.users

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.