Odoo 20 Studio Release Notes

For users

One automation rule can schedule a full plan of activities, possibly for several people, instead of one activity for one person.

For developers

ir.actions.server's Create Activity action gains an activity_plan_id and a plan mode alongside the existing single activity_type_id, reusing the same scheduling logic as the Launch Plan button on a record.

Upgrading from Odoo 19

No migration impact; existing single-activity automations keep working unchanged.

For users

Nothing changes for regular users; this only affects the people who design forms in Studio, who can now rearrange buttons and tabs by dragging them instead of deleting and re-adding them in the right order.

For developers

The form editor's renderer and its drag/drop "hook" component now accept buttons, smart buttons and notebook pages as draggable targets, alongside the fields and groups that were already draggable. The saved view XML only changes in the order of the existing <button> and <page> elements.

Upgrading from Odoo 19

No migration impact; existing forms are unaffected until someone reorders elements in Studio.

For users

No change for end users; the stages themselves still work the same way on the form and in the Kanban view.

For developers

Studio's form editor now renders its own editable version of the statusbar widget (a dedicated component), with a "+ Add stage" affordance and drag handles wired to the same server calls that creating a stage from the Kanban view uses.

Upgrading from Odoo 19

No migration impact; this is a Studio editing convenience, not a change to how stages are stored.

For users

List views that set this keep their important columns readable: a name column will not be squeezed unreadably narrow, and a badge or amount column will not stretch too wide.

For developers

The list renderer's column_width_hook now reads optional min_width/max_width attributes from the <list> field's arch and clamps the resizable column between them. Studio exposes both values together as one "Column Width (px)" field that writes a [min, max] pair.

Upgrading from Odoo 19

No migration impact; existing list views without these attributes behave exactly as before.

For users

Report designers can print a record's tags or other many2many values directly, without first adding a helper field on the model.

For developers

The report editor's field-selector plugin no longer filters out x2many relations when inserting a bare field expression (t-out) into the report body; it inserts the field's raw value, which the developer can still wrap in a template loop for a nicer layout.

Upgrading from Odoo 19

No migration impact; only affects reports edited in Studio going forward.

For users

No change for people who only read or print reports.

For developers

The report editor's tabs (Editor/Preview/Sources) are now built as a proper notebook component instead of ad hoc buttons, and the sidebar reads a "shared block" flag on the selected element to show a caution message before a report designer edits a template used elsewhere.

Upgrading from Odoo 19

No migration impact; purely an editing-experience change inside Studio.

For users

Translators and report designers see each translatable sentence with the surrounding XML around it, making it clear which part of the report a phrase belongs to.

For developers

A dedicated translate_xml component replaces the previous per-field translation approach for report QWeb code, reusing the report's own structure list (report_saleorder, document_tax_totals, and so on) on the left to jump between templates.

Upgrading from Odoo 19

No migration impact; this only changes how translations are edited inside Studio.

For users

Not applicable to regular users; this is a Studio field-creation detail.

For developers

Studio derives the technical name from the field's label at creation time and displays it as a fixed x_studio_ prefix plus an editable slug, so a field named "Venue booking reference" becomes x_studio_venue_booking_reference instead of a generic name like x_studio_char_field_1.

Upgrading from Odoo 19

No migration impact for existing fields, which keep their current technical names; only newly created Studio fields get the friendlier naming.

For users

A date field configured this way shows a warning icon and tooltip as soon as a date on the wrong side of today is entered, catching likely mistakes such as an event date typed in the wrong year.

For developers

DateTimeField gained a warning prop ("none" | "future" | "past") that compares the field's value to today and displays a warning icon; it is set through the widget's options, for example options="{'warning': 'past'}", and Studio's date/datetime field properties expose the same choice as a dropdown.

Upgrading from Odoo 19

No migration impact; the option is off ("No warning") by default, so existing views and data are unaffected until a developer or Studio user turns it on for a field.