This addon allows to define a hierarchy of teams and teams show the related requests
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you organise maintenance teams into parent/child hierarchies, so a parent team automatically shows the requests of all its sub-teams.
This module adds a parent team field to maintenance teams, so you can build a tree of teams (for example a plant team with several line teams below it). The parent team is available on the team form and in the team list, and the list opens the team form directly when you click a row.
Because of this hierarchy, a parent team automatically gathers the maintenance requests belonging to it and to all its child teams. On the team you can see the related requests and several counters for the work still to do: total open requests, requests with a planned date, high-priority requests, blocked requests and unscheduled requests. These counters are recalculated automatically.
When you search maintenance requests by team, the filter now includes the sub-teams of the team you pick, so selecting a parent team returns the requests of its whole branch. The same logic is applied to the dashboard action that lists pending requests for a team.
A team cannot be deleted while another team still depends on it as parent. The module only touches maintenance teams and maintenance requests; no new menus are added.
Depends on
Models and fields (1)
- maintenance.team · extends an existing modelparent_id, parent_path, request_ids, todo_request_ids, todo_request_count, todo_request_count_date, todo_request_count_block, todo_request_count_unscheduled, todo_request_count_high_priority
Text generated by AI (DeepSeek) from reading the Odoo 18.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: 6 confirmed, 3 with no information of 9 versions.
Sources · Odoo 16.0
Confirmed on 2026-11-03 in branch 16.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.