sales_team_progressbar

A progress bar with no maximum is meaningless, so rather than render an empty bar this widget renders a way to fix the problem. It tracks whether the target exists:

useEffect(() => {
    this.state.isInvoicingTargetDefined = this.props.record.data[this.props.maxValueField];
});

and when it does not, offers a link that opens the record:

async defineInvoicingTarget() {
    const { resId, resModel } = this.props.record;
    const action = await this.orm.call(resModel, "get_formview_action", [[resId]]);
    this.actionService.doAction(action);
}

The source comment states the intent plainly: show a progress bar when an invoicing target is defined, or a link redirecting to the record's form view otherwise.

This is a small piece of interface design worth stealing regardless of the widget's fate. An empty metric on a dashboard usually means a missing configuration, and most interfaces respond by showing a zero. A zero looks like bad performance. A link that says the target is not set tells the truth and offers the fix in one click.

If your sales dashboards show zeros that are really missing configuration, that pattern is worth reproducing whether or not you ever used this particular widget.

On a sales team kanban card in Odoo 19:

<field name="invoiced" widget="sales_team_progressbar"
       options="{'max_value': 'invoiced_target'}"/>

In Odoo 20 there is no registration to resolve and the field renders with its default widget.

This removal is part of a larger change to progress bars in Odoo 20, and understanding that is more useful than the single fact.

Three things happened at once. This widget's registration disappeared. So did kanban.progressbar, the view variant it extended, which is notable because most kanban. registrations were renamed to card. rather than deleted; this one has no card. successor at all. And the surviving base progressbar widget lost four of its five options, keeping only max_value and dropping editable, edit_max_value, current_value and overflow_class.

Taken together that is a deliberate simplification of progress bars rather than an incidental cleanup. The kanban-specific rendering is gone and the remaining widget is far less configurable.

Practically, if you used this widget you are not just replacing it, you are also losing the options you would most likely have reached for while rebuilding the same effect. current_value in particular let you display one field while measuring another, which is exactly the sort of thing a custom sales dashboard relies on.

Removed. The registration is absent from the 20.0 branch, as is kanban.progressbar, the variant this widget extended. Unusually for Odoo 20, that kanban variant has no card. replacement, where the other thirteen kanban. registrations were renamed rather than dropped.

The base progressbar widget survives but is much reduced: of its five Odoo 19 options only max_value remains. It is still editable, but that is now driven by the field's readonly state rather than by an option.

Rebuilding the empty-state behavior on Odoo 20 means a custom widget. There is no configuration that reproduces it.