Allow to set the sale order line directly on helpdesk tickets.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you link a sales order item directly to a helpdesk ticket so the time spent on the ticket can be invoiced to the customer.
This module connects helpdesk tickets with sales orders, so the work done on a ticket can be billed to the right customer.
On a helpdesk ticket form, a new "Sales Order Item" field appears when the related project is billable. You can pick the sales order item that the time spent on the ticket should be invoiced against. If you leave it empty, Odoo automatically tries to fill it from the linked task, milestone or project, as long as the customer matches.
The ticket also shows a "Sales Order" field, which is filled automatically based on the chosen sales order item or the project's sales order. If the ticket has no customer yet, Odoo sets it from the sales order. If the customer on the ticket does not match the sales order's customer, invoice or delivery address, the sales order is cleared to avoid billing the wrong company.
In the timesheet list inside the ticket, a "Sales Order Item" column is available (hidden by default) so each time entry can be linked to a specific sales order item. When a timesheet line is created from a ticket, it automatically uses the ticket's sales order item.
All of this only applies when the project is set as billable; otherwise the sales order item is removed and the ticket stays non-billable.
Depends on
Models and fields (1)
- helpdesk.ticket · extends an existing modelsale_line_id, sale_order_id, allow_billable
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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/helpdesk.
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.