Analytic Timesheet In Task
timesheet_task · OCA/timesheet
-
Security25/25No findings
-
Activity0/25Last human commit 121 months ago
-
Required by5/250 modules depend on it
-
Maturity25/25In 5 Odoo series since 6.1
Heuristic over the facts below, not an audit · How it's computed
Migration considerations
HrAnalyticTimesheet— Migrating to 13.0: `@api.multi`/`@api.one` were removed (multi is the default): drop them, looping over `self` where `@api.one` was used. (1 methods) migration-api-multi-one · sourceProjectTask— Class 'ProjectTask' still inherits from the old-style `orm.Model` API: rewrite it against `models.Model`/`models.TransientModel`/`models.AbstractModel` - the old `osv`/`orm` API was removed entirely in modern Odoo. (3 occurrences in this file) migration-old-api-base · sourceProjectTask— Class 'ProjectTask' declares `_columns` as a plain dict: old-style field/default declarations, replace with `fields.X(...)` class attributes and `default=`. (3 occurrences in this file) migration-old-style-fields · source- Since 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp.osv`) (3 occurrences in this file) migration-openerp-import · source
- Raw `cr.execute()` INSERT/UPDATE/DELETE bypasses the ORM (no compute/constrains/tracking/mail): `UPDATE project_task SET remaining_hours=remaining_hours - %s WHERE id=%s` - re-check the table/column names still match after upgrading. (3 occurrences in this file) migration-raw-sql-write · source
- Since 10.0: the `openerp` namespace was renamed to `odoo`; only a deprecated `openerp.addons` alias remained. (`openerp`) migration-openerp-import · source
Migration review checklist, not a compatibility verdict. "Migrating to X.0" applies once you upgrade to that version; "Since X.0" means this version already ignores or rejects that code. Methodology
Description
Replace task work items (project.task.work) linked to task with timesheet lines (hr.analytic.timesheet).
Unless the module project_timesheet, it allows to have only one single object that handles and records time spent by employees, making more coherence for the end user. This way, time entered through timesheet lines or tasks is the same. As long as a timesheet lines has an associated task, it will compute the related indicators.
Used with the module hr_timesheet_task, it also allows users to complete task information through the timesheet sheet (hr.timesheet.sheet).
Dependencies
Code analysis
Extracted from the source by best-effort static analysis (no code is executed); details may be incomplete.
Views touched 2
| XML ID | Name | Model | Type | Status |
|---|---|---|---|---|
view_hr_timesheet_report_search |
hr.timesheet.report.search (timesheet_task) | hr.timesheet.report | search | Inherits hr_timesheet.view_hr_timesheet_report_search |
view_task_form2 |
project.task.form | project.task | form | Inherits project.view_task_form2 |
HTTP endpoints 0
No HTTP endpoints found for this module.
Models touched 4
No new fields.
Public methods (3)-
create(self, cr, uid, vals, context=None) -
unlink(self, cr, uid, ids, context=None) -
write(self, cr, uid, ids, vals, context=None)
No new fields.
Public methods (2)-
on_change_account_id(self, account_id, user_id=False)@api.multiValidate the relation between the project and the task. Task must be belong to the project. -
on_change_unit_amount(self, cr, uid, sheet_id, prod_id, unit_amount, company_id, unit=False, journal_id=False, task_id=False, to_invoice=False, project_id=False, context=None)
-
task_idMany2one → project.taskreadonly=Truestring='Task' args: 'project.task'
No public methods.
No new fields.
Public methods (1)-
write(self, cr, uid, ids, vals, context=None)
Loading…
Loading…
Loading…
Loading…