Manage repair reasons
auto_awesome What this module does
AI-generated from the code · Odoo 16.0Adds a 'Root Cause' field to repair orders and a new configuration menu to manage the list of root causes. Users can pick a reason for each repair and maintain the list of reasons.
This module lets you record why a repair was needed by adding a 'Root Cause' field on repair orders. On the repair order form, the new field appears right after the tags, so you can select one of the predefined root causes.
A new menu 'Repair Order Root Causes' is added under the Repair configuration menu. There you can create, edit and archive the list of root causes. Each root cause has a name (required), a sequence number for ordering, an active flag to archive it, and a company (visible only when multi-company is enabled). The list is shown in a simple tree and form view, with a search view to filter by name, active status or company.
Access is controlled: regular stock users can only read the root causes, while stock managers can create, edit and delete them. The module extends the repair.order model and adds the new repair.reason model.
Depends on
Models and fields (2)
- repair.order · extends an existing modelrepair_reason_id (Root Cause)
- repair.reason · new modelname (Root Cause), active, sequence, company_id (Company)
Text generated by AI (DeepSeek) from reading the Odoo 16.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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/repair.
terminal Installation and usage
OCA documentation · Odoo 16.0Usage
Source · Odoo 16.0Define repair reasons, such as, "Non conformed product". Add this reason in the repair order form view
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.