timesheet_duration_uom

Companies record time differently. Some log hours and minutes, some log fractions of a day, and Odoo stores the underlying number the same way regardless. The display has to follow the setting, otherwise a timesheet is unreadable to the people filling it in.

Odoo has a service that answers which unit is in force and hands back the right component. This widget uses that service and adds one refinement: when the setting is hours and minutes, it asks for an hour-specific component rather than the general one.

The distinction matters because a duration and a time of day format almost identically and mean completely different things. The hour component is written for durations, so a value that exceeds a day still reads as a duration rather than wrapping like a clock.

Timesheet adoption depends on the entry screen matching how people think about their day. A consultancy that bills in days and an agency that bills in hours will both reject a screen that shows them the other unit, and neither will articulate it as a formatting problem; they will just stop filling in timesheets.

What makes this widget worth knowing is that the choice is a single company setting, applied everywhere through a service. If a client asks to change how time is recorded, the answer is a setting rather than a project, provided their custom views use these widgets rather than plain decimal fields.

The core usage

<field name="unit_amount"
       widget="timesheet_duration_uom"
       decoration-danger="unit_amount > 24"
       decoration-muted="unit_amount == 0"/>

The decorations are ordinary list decorations. The widget itself takes no options; the unit comes from the company setting.

Its sibling widgets

# same family, different purposes
timesheet_uom             # the general unit-aware widget
timesheet_uom_no_toggle   # without the unit toggle
timesheet_duration_uom    # this one, hour-aware for durations

Choosing between them is about what the number means, not about how it is stored.

What it is not

<field name="unit_amount" widget="float_time"/>

Always hours and minutes, whatever the company setting says. Correct only where the unit genuinely cannot vary.

The widget is fifteen lines and its whole content is one getter. It asks the timesheet unit service which widget name is configured and, if that name is the hours and minutes format, returns the hour-specific component from the same service. Otherwise it defers to the parent's answer.

Two things follow from that structure. The decision is made at render time, so a change to the company setting takes effect for every field using this widget without any per-view change. And because the component is fetched from the service rather than imported directly, another module can substitute its own implementation for a given unit.

The reason the hour case is special is worth stating plainly. Durations and times of day both format as hours and minutes, but a duration can legitimately exceed twenty four, and it should never be interpreted as a point in the day. The hour component is written with that in mind, which is what the substitution buys.

Everything else, including the toggle behavior and the formatting for other units, is inherited from the general timesheet unit widget.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify the page after release.

Byte-identical. The file on the development branch matches Odoo 19 exactly. Because the widget resolves its component through a service, any change to how timesheet units are rendered flows through without this file changing.