Fieldservice Agreement Repair
This module allows you to link repair.order with an agreement trough a fsm.equipment. This way you can track the repair orders that are covered by an agreement.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Automatically links repair orders created from a field service order to the relevant agreement, so repairs covered by a contract are tracked without manual selection.
This module is a small bridge between field service, repairs and agreements. When a repair order is prepared from a field service order (fsm.order), the module looks for an agreement on the related equipment first, and falls back to the agreement already set on the field service order itself.
If an agreement is found, it is automatically copied onto the repair order being created. This means users do not have to pick the contract by hand when a repair is covered by an agreement.
- The rule applies when repair orders are generated from a field service order.
- Priority is given to the agreement defined on the equipment; if the equipment has none, the agreement of the field service order is used.
- If neither has an agreement, nothing is added and the repair order stays without a contract.
There are no new menus, screens, buttons or reports in this module. It only changes the default values used when a repair order is created, extending the existing fsm.order model. Because it installs automatically, it activates as soon as its dependencies (agreement repair, field service agreement and field service repair) are present.
Models and fields (1)
- fsm.order · extends an existing model
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: 2 confirmed, 7 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/field-service.
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.