mrp_remaining_days_unformatted

Odoo's remaining days widget turns a date into a phrase: today, tomorrow, in five days, three days ago. It also wraps that phrase in a colored badge whose color depends on how close or overdue the date is.

On most screens the badge is the point. On a manufacturing list it is one signal too many, because the rows already carry state coloring, priority markers and availability indicators, and another colored pill makes the whole thing harder to scan.

This widget is the same relative wording without the badge. It changes the template and nothing else, so the phrasing, the thresholds and the language handling all come from the widget it extends.

Visual noise on an operational list is a real cost. A planner scanning fifty manufacturing orders is looking for exceptions, and exceptions only stand out when the baseline is quiet. Removing a badge that repeats information already carried by the row's own state is a small change that makes the important color mean something again.

The practical note is the rename ahead. The behavior survives into the next version under a different name, so this is an upgrade task rather than a feature loss, but a view left unchanged will fall back to the plain date and lose the relative wording entirely.

The usual usage

<field name="date_deadline"
       widget="mrp_remaining_days_unformatted"/>

Relative wording, no badge.

The badged version

<field name="date_deadline" widget="remaining_days"/>

The parent widget, with the colored badge that this one removes.

The plain date

<field name="date_deadline"/>

What a view falls back to if the widget name stops resolving.

The file is six meaningful lines: a subclass that changes the template, and a descriptor that names the component, gives it a display name and declares two supported types.

The interesting part is what the descriptor does not do. It does not spread the parent's descriptor, so the parent's declared options are not inherited. That is a small difference with a real effect: an option that works on the badged widget is not declared here, and the extractor built for it does not run.

Everything about the relative wording itself, including how far ahead or behind a date has to be for each phrase, belongs to the component being extended, so the two widgets always agree on the words even when they disagree on the styling.

The rename on the development branch keeps the behavior and moves it under a name describing relative dates rather than remaining days, which reads as part of a wider tidy-up of that family.

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 this page after the release.

The widget is renamed. On the development branch it lives under a relative-date name in a file of the same shape, with the same behavior. Search custom manufacturing views for the current name before upgrading, because the fallback is a plain date rather than an error.