Skip to Content
Odoo model · Enterprise

aw.rule

ActivityWatch Browser URL Rule. Defined in module timesheet_grid; 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 timesheet_grid

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 aw.rule (18)

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 18 fields
FieldTypeLabelModule1617181920
activebooleantimesheet_gridE
always_activebooleanAlways Activetimesheet_gridE
applies_toselectionApplies Totimesheet_gridE
company_idmany2one res.companyCompanytimesheet_gridE
department_idsmany2many hr.departmentDepartmentstimesheet_gridE
descriptioncharDescriptiontimesheet_gridE
is_editablebooleantimesheet_gridE
is_my_department_rulebooleantimesheet_gridE
match_countintegertimesheet_gridE
namecharNametimesheet_gridE
project_idmany2one project.projectProjecttimesheet_gridE
regexcharRegextimesheet_gridE
sequenceintegertimesheet_gridE
side_activitybooleantimesheet_gridE
task_idmany2one project.taskTasktimesheet_gridE
templatecharTemplatetimesheet_gridE
thresholdfloattimesheet_gridE
typeselectionTypetimesheet_gridE

Related models

Linked by its relational fields: hr.departmentproject.projectproject.taskres.company

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.