Sale Project Timesheet By Seniority
This module adds seniority levels that can be assigned to employees and products.
When an employee timesheets on a specific project this module will checks the project configuration. It looks for an existing mapping for the employee and a sale order line (in the invoicing tab). If no mapping are found one will be automatically created with the first sale order line with the seniority level that corresponds with the seniority level of the employee. If no sale order line fits that criteria one will be created with any product with the correct seniority level and an action for the salesman will be created.
auto_awesome What this module does
AI-generated from the code · Odoo 12.0Add seniority levels to employees and products so that when an employee timesheets on a project, Odoo automatically links the timesheet to the right sale order line or creates one and alerts the salesperson.
This module introduces seniority levels (for example Junior, Senior) that you can assign to employees and to service products. A new menu under Human Resources configuration lets you create and order these levels.
On the employee form you can set a seniority level. On a product, the seniority level field appears only for service products with the 'delivered timesheet' policy, and it is required in that case.
When an employee records a timesheet on a project that is linked to a sale order, Odoo checks the project's sale order lines. If none of the products on the order have a seniority level, nothing happens. If the employee has no seniority level, an error blocks the timesheet and asks the employee to contact HR. If the employee already has a mapping to a sale order line, nothing changes. Otherwise Odoo looks for a sale order line whose product has the same seniority level as the employee and links the employee to that line. If no such line exists, Odoo adds a new sale order line using any product with the matching seniority level (quantity zero) and creates a to-do activity for the salesperson to review that product. If no product with that seniority level exists at all, an error is raised.
Depends on
Models and fields (6)
- sale.order · extends an existing model
- hr.employee · extends an existing modelseniority_level_id
- sale.order.line · extends an existing model
- product.template · extends an existing modelseniority_level_id
- account.analytic.line · extends an existing model
- hr.employee.seniority.level · new modelcode, name, sequence
Text generated by AI (DeepSeek) from reading the Odoo 12.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 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/timesheet.
terminal Installation and usage
OCA documentation · Odoo 12.0Configuration
Source · Odoo 12.0To use this module some seniority levels need to be created. There is a list view for this that can be accessed throught the Configuration menu on the Employee application, it is called Seniority Level.
When the seniority levels are created, they can be assigned to employees and product.
Usage
Source · Odoo 12.0To use this module, you need to:
- When the seniority levels are created and assigned to the employees and products the mapping in the project configuration will be created automatically.
No verified information in OCA: Installation.
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.