Friday, March 26, 2021
14 changes · master
New functionality added to Odoo
Adds tools to classify vendors by 1099 type and export summarized vendor journal entries for a chosen date range. This helps businesses prepare the required CSV data for 1099 e-filing through third-party services, reducing manual reporting work.
Original PR description
This allows vendors to be categorized with a 1099 type. A wizard allows users to export and sum journal items belonging to this vendor in a date range. The generated CSV contains all the information necessary to e-file through a 3rd party service. Task ID: 2222281
Project teams can now better plan work by seeing task dependencies in forecasts and using a Gantt view for tasks outside Field Service. The update also keeps Field Service projects separate from standard project dependency settings and improves scheduling defaults based on working calendars.
Original PR description
Purpose ====== Sometimes, a task can only be completed once another is (e.g. 'install boiler' can only be done once 'order boiler' is complete). Communicating this information is key to organize a project and for the users to know on what they can start working when. ## Settings Project App - Filter the projects to update when the task dependencies feature is enabled in the Project App Settings. We want to check the task dependencies in all existing projects and newly created with is_fsm = False. ## Task views - Add a gantt view on project.task (as in fsm planning, we should display time off in grey and compute default start/end dates based on the company/resource calendar). - The 'hours forecast' stat button should display the shifts linked to the current task + the blocked by tasks + their respective sub-tasks. task-2387984 Community PR: odoo/odoo#66740 Upgrade PR: odoo/upgrade#2203
Enhancements to existing features
Projects now support tasks by default, while field service projects keep their specific task behavior. This reduces confusion around subtasks appearing in project and field service views and aligns the enterprise apps with the wider project management update.
Original PR description
This commit follows the changes introduced by task-2388034. With this commit we want to remove the definition of group project subtask. Tasks are now available by default on each project expect on fsm project task-2388034 : sub-task of : task-2379043 See : https://github.com/odoo/odoo/pull/62577 PR upgrade: odoo/upgrade#1984
Resolved issues and error corrections
This fixes the Belgian salary package configuration for hospital insurance so the benefit is handled correctly. It helps ensure employee salary offers and related HR contract details reflect the proper insurance option.
Miscellaneous changes
cc @jco-odoo @ren-odoo Forward-Port-Of: odoo/enterprise#17312
Original PR description
cc @jco-odoo @ren-odoo Forward-Port-Of: odoo/enterprise#17312
We should call get_warnings on each record in the loop instead of on the whole recordset to avoid a singleton error. opw-2485914 Forward-Port-Of: odoo/enterprise#17314
Sales orders that include campaign tracking details now pass those details to the subscriptions they create. This helps teams connect subscription revenue back to the marketing campaigns or links that generated the original sale.
Original PR description
Propagate UTM from SO to subscriptions taskid: 2457461
Helpdesk teams can now automatically move inactive tickets to a closing stage after a configurable number of days. This reduces manual follow-up work for support agents and helps keep ticket queues cleaner when customers stop responding.
Original PR description
Purpose of the task is, If often happens that a customer stops answering to his ticket when he feels that he was provided a good solution to this problem. In such case, the support agent has to…
Purpose of the task is, If often happens that a customer stops answering to his ticket when he feels that he was provided a good solution to this problem. In such case, the support agent has to manually scan of all the tickets he is in charge of, chase the customer and move the ticket to a closing stage. Support agents would save a lot of time if this process was automated.
so in this commit, added the following setting under helpdesk team:
- name: Automatic Closing
- description: Close inactive tickets automatically
- 'Inactivity period _____ days' field with default value = 7 days
- 'In Stages' m2m, not required; should take all the stages of the
team into account if left empty, and be restricted to the selected stages if set
- 'Move to Stage' m2o required
when a ticket reaches the 'inactivity period' defined (without interruption) in
one of the selected 'in stages' stages, move the ticket automatically to the
'move to stage' stage
- also rename the 'ticket closing' feature into 'Ticket Self-closing'
TaskID: 2466235Users now receive a clear error message when the system cannot find the required numbering sequence for new records. This prevents confusing record names and helps administrators quickly identify and fix missing sequence setup across affected business flows.
Original PR description
Purpose: Display proper error message when sequence not found. Specification: raise error instead of returning FALSE when sequence not found Task-1974068
Original PR description
We should call get_warnings on each record in the loop instead of on the whole recordset to avoid a singleton error. opw-2485914 Forward-Port-Of: odoo/enterprise#17314
Before this commit, on mobile with an RTL language, the "back-arrow" in the breadcrumb wasn't pointing to the right direction (i.e. kept the left direction of LTR language). This commit properly rotates it depending on the language direction. Steps to reproduce: 1. Login with an user with RTL language (like Arabic) 2. Go to project apps > 3. Open a task 4. The display arrow for going back to the previous view isn't in the right position => Bug Task ID: 2361323 Forward-Port-Of:
Original PR description
Before this commit, on mobile with an RTL language, the "back-arrow" in the breadcrumb wasn't pointing to the right direction (i.e. kept the left direction of LTR language). This commit properly rotates it depending on the language direction. Steps to reproduce: 1. Login with an user with RTL language (like Arabic) 2. Go to project apps > 3. Open a task 4. The display arrow for going back to the previous view isn't in the right position => Bug Task ID: 2361323 Forward-Port-Of: odoo/enterprise#17285
This solves a problem in test data for document type 110 (lack of city "Scranton" Forward-Port-Of: odoo/enterprise#17226
Original PR description
This solves a problem in test data for document type 110 (lack of city "Scranton" Forward-Port-Of: odoo/enterprise#17226
### Task 452 **Description of the issue/feature this PR addresses:** For the new service digital VAT Book from AFIP, it is mandatory present the txt files preserving the original amount for each currency **Current behavior before PR:** If you have an invoice with a different currency than the one in your company, when you get the txt files to import in AFIP the values are translated to the company currency. **Desired behavior after PR is merged:** If you have an invoice with a diffe
Original PR description
### Task 452 **Description of the issue/feature this PR addresses:** For the new service digital VAT Book from AFIP, it is mandatory present the txt files preserving the original amount for each currency **Current behavior before PR:** If you have an invoice with a different currency than the one in your company, when you get the txt files to import in AFIP the values are translated to the company currency. **Desired behavior after PR is merged:** If you have an invoice with a different currency than the one in your company, when you get the txt files to import in AFIP it keeps the original amounts. Forward-Port-Of: odoo/enterprise#15911
Currently, the timer is not displayed as running in kanban view of timesheet even it's started. So in this commit, * Prevent that the timer is only shown after 1 sec when page is loaded by outsourcing the refresh functionnality and caling it directly before creating the interval. * Ensure that the time is always correct (even when blocking the JS thread like in debug, or who knows for any reason) by computing it in each interval. * Move the layout change before the interval star
Original PR description
Currently, the timer is not displayed as running in kanban view of timesheet even it's started. So in this commit, * Prevent that the timer is only shown after 1 sec when page is loaded by outsourcing the refresh functionnality and caling it directly before creating the interval. * Ensure that the time is always correct (even when blocking the JS thread like in debug, or who knows for any reason) by computing it in each interval. * Move the layout change before the interval starts TaskId : 2472756 Forward-Port-Of: odoo/enterprise#17304
- Go to Accounting > Customers > Invoices - Create an invoice and register paymnent - Go to Accounting > Reporting > Cash Flow Statement The account move lines linked to the payment do not appear in the report. Since this commit https://github.com/odoo/enterprise/commit/faa703057fbcd4036befc8654dd2816e529397ec#diff-2b5df4f7b5c6c8a0138101b2f104476c8fe0cab00191df361073176158fcf742R118, only the account move lines linked to the default account of the journal are displayed. opw-2451173 Fo
Original PR description
- Go to Accounting > Customers > Invoices - Create an invoice and register paymnent - Go to Accounting > Reporting > Cash Flow Statement The account move lines linked to the payment do not appear in the report. Since this commit https://github.com/odoo/enterprise/commit/faa703057fbcd4036befc8654dd2816e529397ec#diff-2b5df4f7b5c6c8a0138101b2f104476c8fe0cab00191df361073176158fcf742R118, only the account move lines linked to the default account of the journal are displayed. opw-2451173 Forward-Port-Of: odoo/enterprise#17202