395db264bb5e2b27ae9d1a23605ae0ccf4c668df
Impacted modules: hr_timesheet, sale_timesheet and project. This merge commit provides feature for service flow (selling timesheet). The most important points are 1/ selling project based on template: on product configuration, user can now set a template for the Sales Order to create a project by duplicating this ones (stages, tasks, ... are duplicated from the template). If several Sale Lines are based on the same template, only one will be created. Same mecanism if multiple product creating a project without template: only one project per SO. 2/ Project Overview Revamp: before this, it was based on a filter domain on analytic line (aka timesheet). This causes many problem as if you are selling prepaid services, you project plan was empty as long as no timesheet was created. Moreover, this kind of domain is not very usefull for the user (nobody want to see project plan of timesheet containing "analysis" for instance). The project plan is now a filter on project, to ease fetching data from the project (even if no timesheet or forecast), and allow cross project analysis. The overview table part is now available even when forecast is not installed. 3/ Assign Tasks Massively: a wizard is provided to ease linking task to the same Sale Order Line, to ease billing their related timesheets. 4/ Usability Details: filter task per SO or SO line, stat button on Sale Order now redirect to kanban project instead of global project plan, generated task/project names are cleaner, ... 5/ Installing only timesheet module, user will be able to track cost without selling time. Fields of cost and employee hourly cost are moved from sale_timesheet to hr_timesheet. To make this feature works, some technical efforts was required: 1/ Project and Analytic Account: To allow SO to generate multiple project, we wanted them to share the same analytic account (the one of the Sale Order). To do so, we had to remove the inheritS between project.project and account.analytic.account models. To allow timesheet on a project, an analytic need to be set manually, or it will be automatically generated (like before with the inheritS), if allow_timesheet is checked. 2/ Refactoring of SOL service generation: to allow SOL to generate only one project (per template) for the SO, the part of service creation on sale.order.line needed a refactoring. 3/ Revamping the overview also improve its performances: some part are now based on SQL queries (table part), or on report (profitability report). Doing a report allow the user to create its own filters, and give him a more accurate tools to extract statistics then project plan. The idea is to get only one source of information for reporting and analysis. Please see sub commits for more details. Thanks for @tde-banana-odoo for his review and advices during development, and thanks to @bst-odoo for his functionnal ideas, testing and support. Tasks #34702 Closes #22268
…
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, Purchase Management, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
Then follow the developer tutorials
Languages
Python
49.6%
JavaScript
47.8%
SCSS
2%
CSS
0.3%
HTML
0.2%