hr_presence_status_private

In Odoo 19 this is an empty subclass. The whole file is a class that adds nothing, a descriptor that swaps in that class, and one registration:

export class HrPresenceStatusPrivatePill extends HrPresenceStatusPill {}

export const hrPresenceStatusPrivatePill = {
    ...hrPresenceStatusPill,
    component: HrPresenceStatusPrivatePill,
};

registry.category("fields").add("form.hr_presence_status_private", hrPresenceStatusPrivatePill);

All the visible behavior comes from the pill it extends, which renders the status as a rounded outline button and picks the color from the value: success for present, warning for absent, muted secondary for out of working hours or archived.

The separate class exists so that other modules can patch the private variant without affecting the public one.

Presence status is one of the more sensitive things an HR screen displays, which is why Odoo keeps a separate private variant at all. The variant is the hook a module uses to show more to an HR officer than to a colleague.

What matters for a rollout is that this widget is not used anywhere in standard Odoo. If you see presence indicators on your employee screens, they are coming from a different widget in the same family. This one exists as an extension point.

In Odoo 19, on an employee form. The prefix is chosen by the view, so you write the bare name:

<field name="hr_presence_state" widget="hr_presence_status_private"/>

In Odoo 19 that same line in a list view resolves to nothing, because no unprefixed registration exists. In Odoo 20 it works in both.

Two changes land together, and only one of them is obvious.

The obvious one is scope. Odoo 19 registers form.hr_presence_status_private and nothing else. When Odoo resolves a widget it tries the view-prefixed key first and then the bare one, so in a list or kanban view there is no match at all and the field falls back to its default rendering. Odoo 20 registers the bare hr_presence_status_private, so it resolves everywhere.

The quiet one is appearance. In Odoo 19 the class extends the pill:

export class HrPresenceStatusPrivatePill extends HrPresenceStatusPill {}

In Odoo 20 it extends the base status component instead:

export class HrPresenceStatusPrivate extends HrPresenceStatus { }

HrPresenceStatusPill is what supplies the rounded outline button and the btn-outline-success and btn-outline-warning color classes. Extending the base instead means that styling is gone in Odoo 20.

So a field that showed a colored pill in Odoo 19 shows the plain status rendering after an upgrade. Nothing errors, no option changed, and a diff of the registration alone would report only the prefix change. The visual difference only shows up if you read which class is being extended.

If your database patches this widget, check the patch too: it was written against a subclass of the pill and now sits on a subclass of the base.

The form. prefixed registration is removed and replaced by a bare hr_presence_status_private, so the widget becomes usable in every view rather than forms only. The file also moves, from components/hr_presence_status_private_pill/ to components/hr_presence_status_private/.

Alongside that, the component's base class changes from HrPresenceStatusPill to HrPresenceStatus, which removes the rounded pill styling and its outline colors. Expect the indicator to look different after an upgrade even though no option changed.

The sibling hr_presence_status keeps its own form. variant, so the two are no longer registered the same way.