picking_type_dashboard_graph

The Inventory Overview shows one kanban card per operation type, receipts, deliveries, internal transfers, and each card carries a small bar chart of transfer volume across six date buckets. That chart is picking_type_dashboard_graph, bound to the kanban_dashboard_graph text field whose value is JSON computed server side: an array of points with a label, a value and a bucket type.

The widget extends the generic dashboard_graph journal widget from the web module and overrides only the bar chart configuration. The override adds a third color bucket, present, on top of the base widget's past and future, and, more importantly, an onClick handler that turns the chart into navigation.

For an inventory manager the chart is a workload radar: the leftmost bar is your backlog (late transfers), the middle bars show today's load, and the right side previews what is coming. Because every bar is a filter shortcut, the overview doubles as triage: click the late bar on Deliveries and you are looking at exactly the overdue delivery list, with the operation type already filtered.

The color semantics carry meaning at a glance: past, present and future buckets each render in a distinct palette color, and dark mode is handled through the color scheme cookie.

<!-- Core usage on the operation type kanban (stock module) -->
<field t-if="!selection_mode" name="kanban_dashboard_graph"
       graph_type="bar" widget="picking_type_dashboard_graph"/>

The JSON in the field must be an array whose first entry holds values (points with label, value and a type of past, present or future) plus the picking_type_id that the click handler forwards to the action.

The click handler is a hardcoded map worth knowing when you extend the dashboard: column index 0 through 5 translate to the filter names before, yesterday, today, day_1, day_2 and after, and the handler fires the stock.click_dashboard_graph action with search_default_<bucket> plus the operation type preset in the context. Add a seventh bar server side and clicks on it map to nothing.

The guard is equally simple: if the chart config carries no pickingTypeId, which is how sample data for empty databases arrives, the click returns early. Repair and Manufacturing reuse the widget unchanged on their own operation type cards, which is why the usage count spans three modules.

Before 18.0 the operation type kanban carried no chart at all (the only dashboard-ish thing in the 16 and 17 views is a CSS class). The JSON field, the server computation and this widget all arrived together in 18.0, and the file has not changed by a byte since.

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.

The file is byte-identical to Odoo 19.0 on the development branch: same buckets, same click map, same colors. The neighboring dashboard ecosystem does move, the account module grows its own journal graph variant, but this widget is untouched. We re-verify after the release.