MuK Tree List
muk_web_tree
Adds a tree list view for hierarchical records
Nest your records under their parents, in one list.
A new view type for any model that points to itself — categories, contacts, departments, locations. Rows open like folders, and everything a list can do, from inline editing to sums, still works.
The top level is paged like any list. The children of a row are read in one call when you open it.
Every match stays at its own depth, under its parents, so you see where it sits and not only that it exists.
Drop a row on another to move it there. A record can never end up inside one of its own children.
A list that knows its hierarchy
Everything else is the list view you already know: columns, widgets, sums, buttons, decorations and inline editing.
Each record sits indented under its parent, with a chevron to open it. The rows you opened stay open the next time.
Matches stay in the tree. The parents that lead to them are shown greyed out and opened for you.
The + on a row starts a record right under it, with the parent filled in, edited inline or in the form.
Drop a row on another to move it beneath, or on its upper or lower edge to make the two siblings.
Mark a numeric column as a rollup and every parent row shows the total of its whole subtree.
Right opens a row, Left closes it or jumps to its parent, and each row tells assistive technology its level.
Find a record without losing its place
A flat search result tells you what matched and nothing about where it lives. The tree list keeps every match at its own depth and brings the parents along, greyed out and in italics, opened down to the match. Clear the search and the tree is back as you left it.
Add it where it belongs
Hover a row and click + to start a record directly beneath it, with the parent already set. On an editable tree you type into the row and save; otherwise the form opens, prefilled. Moving a record later is a drag of its handle onto the new parent.
A record can not be dropped onto one of its own descendants, so a drag never cuts a branch off the tree.
Put it on any hierarchy
The module brings the view type, not the views. A <treelist> goes next to the list and form an action already has, on whichever models your teams browse as a hierarchy.
The tree follows parent_id, or any many2one to the same model named in parent_field.
Add rollup="1" to a numeric field and parents show the total of their subtree, in the row and in the footer.
Group the view by a field and every group shows its records as a tree, with its own pager for the top-level rows.
Help and support
What you get for free, and what has to be paid work.
Issues and merge requests are welcome on the public repository. They are read — but no response time is promised.
A tree list set up on your own models, or a fix on a deadline, is paid work — quoted up front. Write to sale@mukit.at.
LGPL-3. Use it, change it, ship it inside your own work — no licence key, no database count.
Want more?
MuK IT — Austrian Odoo partner, ViennaModules written for your process, on your Odoo version.
Odoo joined up with the systems you already run.
Hosting, deployment and upgrades you do not have to watch.
Your team taught the parts of Odoo they actually use.
An agreement, so an answer does not depend on who is free.
Documentation
The full text is on the Documentation tab, and in doc/ inside the download.Odoo.sh or on-premise, Community or Enterprise.
A treelist view on the action, and the attributes it takes.
Depends on muk_web_group alone, nothing external.
Opening rows, searching, adding children, dragging and the keyboard.
Open rows are kept in the browser, so an upgrade has nothing to migrate.
MuK IT GmbH, Vienna. Author and maintainer.
Which of your records have parents?
Tell us which hierarchies your teams still scroll through as flat lists, and we will tell you where a tree list saves them the search. MuK IT — Austrian Odoo partner, Vienna.
Ce que l'application ne fait pas
L'éditeur n'a pas encore publié la liste de ce que l'application ne fait pas. C'est une règle du magasin : demandez-la au support avant de vous engager.
Applications du magasin nécessaires
- MuK Groups
muk_web_group - MuK Refresh
muk_web_refresh
Modules Odoo Community utilisés
base_import
Applications qui la complètent
| Série | Version | État | Publiée le |
|---|---|---|---|
| 20.0 | 20.0.1.0.5 | Disponible | 27/09/2026 |
Fiche générée depuis julien2364/omnifloo-tiers-muk-it-odoo-modules (branche 20.0, commit 5bd298c18a48).
Contrôle automatique du magasin (distinct de l'éditeur), appliqué à toutes les applications. Conforme.
| Contrôle | Résultat | Effet si absent |
|---|---|---|
| Manifeste lisible sans exécution | conforme | bloquant |
| Licence reconnue (LGPL-3) | conforme | bloquant |
| Aucune dépendance vers Odoo Enterprise | conforme | bloquant |
| Aucun import de code Enterprise | conforme | bloquant |
| Aucun en-tête de licence Enterprise | conforme | bloquant |
| Icône static/description/icon.png | conforme | déclasse |
| Description (static/description/index.html ou README) | conforme | déclasse |
| Tests automatisés (tests/test_*.py) | conforme | déclasse |
| Traduction française (i18n/fr.po) | conforme | info |
| Section « Ce que le module ne fait pas » | absent | info |
Avis des clients connectés. Un avis noté par client ; l'éditeur peut y répondre. Connectez-vous pour laisser un avis.
- Éditeur
- MuK IT GmbH
- Signaler un problème
- https://github.com/muk-it/odoo-modules
- Clients Omnifloo
- Support inclus selon votre formule : centre d'aide.