Skip to Content
Odoo model · Enterprise

appointment.leave

Closing days for appointments and their users / resources. Defined in module appointment; exists in Odoo 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

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

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 19 to 20

Community + Enterprise All changes in this step

New model in Odoo 20.

All fields declared on appointment.leave (11)

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 11 fields
FieldTypeLabelModule1617181920
appointment_type_domaincharappointmentE
appointment_type_idsmany2many appointment.typeAppointmentsappointmentE
date_fromdatetimeStart DateappointmentE
date_todatetimeEnd DateappointmentE
has_appointment_type_tz_mismatchbooleanappointmentE
leave_reasoncharReasonappointmentE
leave_typeselectionappointmentE
resource_domaincharappointmentE
resource_idsmany2many appointment.resourceResourcesappointmentE
user_domaincharappointmentE
user_idsmany2many res.usersUsersappointmentE

Related models

Linked by its relational fields: appointment.resourceappointment.typeres.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.