OdooWiki OCA HUB

Agreement Helpdesk Mgmt Fieldservice

agreement_helpdesk_mgmt_fieldservice folder_open OCA/agreement open_in_new
Uncategorised License: AGPL-3

Propagates the helpdesk ticket's agreement when creating a FSM Order.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

When a helpdesk ticket linked to an agreement creates a Field Service order, the same agreement is automatically carried over to the new order.

This module is a small bridge between helpdesk tickets, agreements and Field Service orders. It does not add any new screen or menu of its own; it changes what happens when a user uses the existing "create order" action on a helpdesk ticket.

  • If the helpdesk ticket is linked to an agreement, that agreement is automatically pre-filled on the Field Service order that is created from the ticket.
  • If the ticket has no agreement, nothing changes and the order is created as usual.

The module works on the helpdesk.ticket model and extends the action_create_order method, which is the button/action that turns a ticket into a Field Service order. It relies on the agreement link already provided by the related agreement and helpdesk modules.

Because it is set to install automatically, it activates as soon as its dependencies are present, so users do not need to install it manually. The practical benefit is less manual data entry and fewer mistakes: the agreement that covers the customer's work is kept consistent between the ticket and the resulting Field Service order.

Models and fields (1)
  • helpdesk.ticket · 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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

Sources · Odoo 18.0

Confirmed on 2026-11-03 in branch 18.0 of OCA/agreement.

terminal Installation and usage

No verified information

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.

info

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.