priority

Odoo's stars are not a rating widget bolted on; they are a thin skin over an ordinary selection field. The widget reads the field's selection list, treats the first value as "no priority", and draws one clickable star per remaining value. CRM's classic definition, 0 Normal, 1 High, 2 Very High, 3 Urgent, renders as three stars.

Interaction is tuned for speed, verified in the source. A click writes the value and, with autosave at its default, saves the record on the spot, list views included. Clicking the star that is already active resets the field to the first selection value, so un-starring needs no extra control. Hovering previews the level before you commit.

Priority stars work because they cost one click and are visible from across the room. A pipeline where urgent leads carry stars gets triaged by eye; kanban cards sort and group by the same field; and because it is just a selection underneath, filters, automations and reports treat it like any other value.

Two decisions make or break the feature. Keep the scale short: one or two stars is a signal, five is a debate nobody wins, and the widget will happily render however many your selection defines. And agree on meaning: "starred means the founder asked" beats "starred means important" every time. The clear-by-reclick gesture matters operationally too, since stale urgency is worse than none; teams should un-star as reflexively as they star.

The instant save is the same trade as the toggle widget: automations watching priority fire at the click, which is usually exactly what an escalation flow wants.

Studio applies this widget without code.

1. Open the view in Studio and select the selection field (or create one whose first value is the neutral state).

2. In Properties, set Widget to Priority. The Autosave option Studio shows corresponds to the option below.

The star count and labels are the selection's values, edited on the field, not the widget. Anything conditional, hiding stars per state, restricting who may set Urgent, is view attributes or record rules, one step beyond Studio's panel.

The standard CRM-style field

priority = fields.Selection([
    ("0", "Normal"),
    ("1", "High"),
    ("2", "Very High"),
    ("3", "Urgent"),
], default="0")

Three stars; the first value is the empty state and the default.

In the view

<field name="priority" widget="priority"/>

A single favorite star

starred = fields.Selection([("0", "Normal"), ("1", "Starred")], default="0")

Two values render as one star, a lightweight flag pattern. For booleans, boolean_favorite does the same without a selection.

Without instant saving

<field name="priority" widget="priority"
       options="{'autosave': False}"/>

On form views the widget registers a command, verified in the source: Set priority..., category smart action, hotkey Alt+R.

Press it with a record open and the command palette lists every selection label, Normal through Urgent; pick one and the same update-and-save path runs as if you had clicked the star. Together with the statusbar's Alt+X family, it makes full keyboard triage of a queue realistic: open, Alt+R, choose, next.

Worth knowing about the gesture set: the click handler is where clear-by-reclick lives, comparing the clicked value with the current one and resetting to options[0] on a match. If users report "my star disappeared", they double-set the same level; that is the un-star working.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The changes below are read from the public development branch and are not final until release.

Nothing changes for this widget. Same single option and default, same clear-by-reclick, same Alt+R command. Internal syntax moves to the new Owl props system, affecting JavaScript patches only. We re-verify once Odoo 20 ships.