With Odoo version 13 a new feature is added which allows kanban views to be extended by a search panel. This can be defined via XML and is then automatically added to the view. With this module the function is ported back to version 12.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Adds a side search panel to kanban views, letting users filter records by categories and multi-value filters directly from the kanban screen, a feature normally only available in Odoo 13 and later.
This module brings the Odoo 13 kanban search panel back to Odoo 12. On any kanban view that declares a searchpanel section in its XML, a panel appears on the left of the kanban board.
- Categories: a field shown as a category (default) lets users pick one value at a time; values can be hierarchical (parent/child) and are shown as a foldable tree. The chosen value is remembered in the browser's local storage, so it is restored when the view is reopened.
- Filters: a field marked with
select="multi"becomes a filter where several values can be ticked at once. Filters can show a count of matching records, can be grouped by another field, and can be hidden when empty. - The panel combines the selected categories and filters into a domain that is applied together with the normal search bar filters, and the kanban reloads automatically when a selection changes.
- On mobile devices the panel is shown as a collapsible summary with breadcrumbs.
The module extends the generic base model with two helper methods, search_panel_select_range and search_panel_select_multi_range, used to fetch the possible values and their counters. It also ships a demo view that adds language and timezone filters to the Users kanban view.
Depends on
Models and fields (1)
- base · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 12.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/web.
terminal Installation and usage
OCA documentation · Odoo 12.0Usage
Source · Odoo 12.0This tool allows to quickly filter data on the basis of given fields. The fields are specified as direct children of the searchpanel with tag name field, and the following attributes:
name(mandatory) the name of the field to filter onselectdetermines the behavior and display.groups: restricts to specific usersstring: determines the label to displayicon: specifies which icon is usedcolor: determines the icon color
Possible values for the select attribute are
one(default) at most one value can be selected. Supported field types are many2one and selection.multiseveral values can be selected (checkboxes). Supported field types are many2one, many2many and selection.
Additional optional attributes are available in the multi case:
domain: determines conditions that the comodel records have to satisfy.
A domain might be used to express a dependency on another field (with select="one") of the search panel. Consider
<searchpanel>
<field name="department_id"/>
<field name="manager_id" select="multi" domain="[('department_id', '=', department_id)]"/>
</searchpanel>In the above example, the range of values for manager_id (manager names) available at screen will depend on the value currently selected for the field department_id.
groupby: field name of the comodel (only available for many2one and many2many fields). Values will be grouped by that field.disable_counters: default is false. If set to true the counters won't be computed.
This feature has been implemented in case performances would be too bad.
Another way to solve performance issues is to properly override the search_panel_select_multi_range method.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.