TODO: add repo description.
addon | version | maintainers | summary |
---|---|---|---|
base_territory | 14.0.1.0.0 | This module allows you to define territories, branches, districts and regions to be used for Field Service operations or Sales. | |
fieldservice | 14.0.1.19.0 | Manage Field Service Locations, Workers and Orders | |
fieldservice_account | 14.0.1.2.1 | Track invoices linked to Field Service orders | |
fieldservice_account_analytic | 14.0.1.0.0 | Track analytic accounts on Field Service locations and orders | |
fieldservice_account_payment | 14.0.1.0.1 | Allow workers to collect payments from the order. | |
fieldservice_activity | 14.0.1.0.0 | Field Service Activities are a set of actions that need to be performed on a service order | |
fieldservice_agreement | 14.0.1.1.1 | Manage Field Service agreements and contracts | |
fieldservice_calendar | 14.0.1.0.0 | Add calendar to FSM Orders | |
fieldservice_crm | 14.0.1.1.0 | Create Field Service orders from the CRM | |
fieldservice_delivery | 14.0.1.0.0 | Select delivery methods and carriers on Field Service orders | |
fieldservice_distribution | 14.0.1.0.1 | Manage your distribution structure | |
fieldservice_equipment_stock | 14.0.1.1.0 | Integrate stock operations with your field service equipments | |
fieldservice_isp_account | 14.0.1.0.1 | Invoice Field Service orders based on employee time or contractor costs | |
fieldservice_isp_flow | 14.0.1.0.0 | Field Service workflow for Internet Service Providers | |
fieldservice_maintenance | 14.0.1.0.0 | Integrate Field Service orders with maintenance requests | |
fieldservice_partner_multi_relation | 14.0.1.0.1 | Manage relations between contacts, companies and locations | |
fieldservice_project | 14.0.1.0.1 | Create field service orders from a project or project task | |
fieldservice_purchase | 14.0.1.0.1 | Manage FSM Purchases | |
fieldservice_recurring | 14.0.1.6.0 | Manage recurring Field Service orders | |
fieldservice_repair | 14.0.1.0.0 | Integrate Field Service orders with MRP repair orders | |
fieldservice_route | 14.0.1.0.0 | Organize the routes of each day. | |
fieldservice_sale | 14.0.1.3.1 | Sell field services. | |
fieldservice_sale_recurring | 14.0.1.0.0 | Sell recurring field services. | |
fieldservice_sale_stock | 14.0.1.0.0 | Sell stockable items linked to field service orders. | |
fieldservice_size | 14.0.1.0.1 | Manage Sizes for Field Service Locations and Orders | |
fieldservice_skill | 14.0.1.0.0 | Manage your Field Service workers skills | |
fieldservice_stage_server_action | 14.0.1.0.0 | Execute server actions when reaching a Field Service stage | |
fieldservice_stage_validation | 14.0.1.0.0 | Validate input data when reaching a Field Service stage | |
fieldservice_stock | 14.0.1.2.1 | Integrate the logistics operations with Field Service | |
fieldservice_substatus | 14.0.1.1.0 | Add sub-statuses to Field Service orders | |
fieldservice_timeline | 14.0.1.4.0 | This module is a display timeline view of the Field Service order in Odoo. | |
fieldservice_vehicle | 14.0.1.0.0 | Manage Field Service vehicles and assign drivers | |
fieldservice_vehicle_stock | 14.0.1.1.0 | Track inventory of Field Service vehicles |
This repository is licensed under AGPL-3.0.
However, each module can have a totally different license, as long as they adhere to Odoo Community Association (OCA)
policy. Consult each module's __manifest__.py
file, which contains a license
key
that explains its license.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.