Maintenance Equipment Category Hierarchy
Equipment Categories Hierarchy
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you organise maintenance equipment categories into a parent/child tree, so you can group related categories and filter maintenance requests by a whole branch of categories.
This module turns the flat list of equipment categories into a hierarchy. On each category you can now set a Parent Category, and the form shows its Child Categories as tags. The full path of a category is built automatically (for example "Parent / Child") and is used as the category's display name, so you can recognise where a category sits in the tree.
Where it appears in Odoo: - The equipment category list view gains a Parent Category column. - The equipment category form shows Parent Category and Child Categories fields. - The maintenance request search view changes the category filter so that choosing a category also finds requests belonging to its sub-categories.
Business rules and automatic behaviour: - The complete name is computed from the parent's complete name plus the category name. - Odoo blocks recursive categories: you cannot make a category a parent of itself, directly or through a chain, and an error message is shown. - Deleting a parent category also deletes its child categories.
The module extends the maintenance.equipment.category model and adjusts the search view of maintenance.request.
Depends on
Models and fields (1)
- maintenance.equipment.category · extends an existing modelchild_id, parent_id, parent_path, complete_name
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 5 confirmed, 4 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/maintenance.
terminal Installation and usage
No verified informationInstallation 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.