gauge

The gauge widget renders a numeric field as a speedometer: a doughnut chart cut to 180 degrees, the value arc in blue against a gray remainder, with the value formatted human-readably, one decimal, in the center and a title above. It lazy-loads Odoo's bundled Chart.js on first render and rebuilds the chart on every data change.

The maximum comes from one of two places: a companion field on the same record, via the max_field option, or a static max_value that defaults to 100. Tooltips on the two arc segments show the raw value and the maximum.

Gauges answer one question at a glance: how full is this against its target? That makes the widget a natural fit for quota-style dashboards, which is exactly how CRM uses it, showing each salesperson's leads assigned this month against their monthly cap on the team member kanban. Anywhere you keep a target column next to an actual column, a gauge on the kanban card communicates progress faster than two numbers.

The self-healing scale cuts both ways. Because the widget silently raises the maximum to the value when exceeded, a rep at 130 percent of quota shows a full-looking gauge rather than an alarming overflow. If overshoot needs to be visible, pair the gauge with a decoration or pick a widget that shows saturation differently, like percentpie.

The core pattern: value against a quota field

<field name="lead_month_count"
       widget="gauge"
       options="{'max_field': 'assignment_max'}"
       invisible="assignment_max == 0"/>

Straight from the CRM team member kanban. Note the guard: with a zero quota the gauge is hidden rather than rendered empty. The max field must be loaded in the same view, invisibly if necessary.

Fixed scale with a title

<field name="satisfaction_pct"
       widget="gauge"
       options="{'max_value': 100, 'title': 'Satisfaction'}"/>

Without a title option the widget falls back to the field's label. Without max_value the scale is 0 to 100 anyway, since 100 is the default.

The gamification goal kanban, the widget's other core usage, passes options="{'max_field': 'target_goal', 'label_field': 'definition_suffix', 'style': 'width:160px; height: 120px;'}". Only the first key does anything. label_field and style belonged to the pre-Owl gauge implementation and have not been read since at least Odoo 16, yet the view still ships them on the development branch. It is a handy reminder that options in core views are not proof an option exists; the widget source is.

Two smaller behaviors from the same function: the maximum is computed as Math.max(value, max), which is the self-healing scale described above, and a gauge whose value and maximum are both zero is rendered against a scale of 1 with the tooltip still reporting 0, so an empty gauge draws as an empty arc instead of dividing by zero.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and the notes below are provisional until release, when this page is re-verified.

One real addition is visible: a max_tooltip option, declared and extracted, that replaces the maximum shown in the tooltip with a custom string. The rendering moves to a shared useChart hook and the new props API, internals only. And the two quirks documented above survive: extractProps still reads max_field while the metadata still declares max_value_field, and the gamification view still ships its dead options.