Since we dropped support for inherits the user interface in the project module is quite wired. You need to create a work for a project (typically using the m2o field) and you cannot have to projects pointing to the same work (which is quite logical). We created a small module to hide [1] those details from the user but I'm not still very happy with the current design.
After all, if work is meant to be used as a lightweight version of a task why would we want it to be a hierarchy? Wouldn't it be better if we remove the "work" field from timesheet.line and replace it with a field of type reference which allows selecting tasks or other kind of models? This would allow to have all the time-related information from employees in a single place no matter if the work was in a project.work or the "production" equivalent. We could also create a timesheet.work for each production work but there the hierarchy and some other fields of the model seem overkill. Maybe the problem is that I don't fully understand what work should be used to and why those timesheet_available, timesheet_start_date and timesheet_end_date would be necessary in the base module... [1] https://bitbucket.org/nantic/trytond-project_auto_timesheet -- Albert Cervera i Areny Tel. 93 553 18 03 @albertnan www.NaN-tic.com
