Skip to Content
Odoo model · Enterprise

hr.appraisal.template

Employee Appraisal Template. Defined in module hr_appraisal; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 3 fields added, 0 removed, 0 renamed.

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

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

Fields added (3)

FieldTypeModule
department_idsmany2manyhr_appraisal
sequenceintegerhr_appraisal
survey_template_idsmany2manyhr_appraisal_survey

Odoo 19 to 20

Community + Enterprise All changes in this step

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

All fields declared on hr.appraisal.template (7)

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 7 fields
FieldTypeLabelModule1617181920
appraisal_employee_feedback_templatehtmlEmployee Feedbackhr_appraisalE
appraisal_manager_feedback_templatehtmlManager Feedbackhr_appraisalE
company_idmany2one res.companyhr_appraisalE
department_idsmany2many hr.departmentDepartmentshr_appraisalE
descriptioncharShort Namehr_appraisalE
sequenceintegerhr_appraisalE
survey_template_idsmany2many survey.survey360 Feedback Surveyhr_appraisal_surveyE

Related models

Linked by its relational fields: hr.departmentres.companysurvey.survey

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.