Monday, February 3, 2020
14 changes
Enhancements to existing features
Leave request names now include the relevant date range, making it easier for managers and team members to understand when the time off is scheduled without opening the full record. This also makes notification emails clearer and more immediately useful.
Original PR description
Before this commit, the date range was not known without open the record in backend. It is really painfull to don't know when a guy of your team ping you on a new leave the date from the current leave. (today ? next week ? ...) Now we have the date into the name_get and so the subject of the email. task-2001439 Nothing related to next activity ;) but idea was the same. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This change lets stock operations skip automatic SMS notifications when another workflow, such as field service, handles communication separately. It helps avoid duplicate or unnecessary customer messages and also includes a small safeguard against a calculation error in stock accounting.
Original PR description
In stock, before sending an sms, we check if there aren't the key 'skip_sms' in the context. It is useful, for example, in FSM. application. TaskID: 2081191 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Timesheets can now use the analytic account set on the sales order or task instead of always inheriting the project account. This helps businesses track costs and revenue more accurately when projects contain tasks for different customers.
Original PR description
Purpose ======= Currently, it is only possible to set an Analytic Account for a whole Project, there is no distinction by task. However, if the user has 1 task per customer, he cannot track the costs and revenues for that specific customer easily. He has to manually change the AA of the timesheets' analytic lines. An option would be to set a different AA on the SO generating the task, but the AA of the project takes over anyway. Specifications ============== If the user sets an AA on the SO, it should bypass the one set on the project Add an AA field below the Email cc one on tasks in debug mode - should be related to the AA field from the SO - it should also bypass the AA set on the project All the timesheets from this task should be related to the AA field set on the SO/Task -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When the sale_timesheet app is installed, new projects will have time tracking timers enabled automatically. This reduces setup steps for teams that sell services and need to track work time against projects from the start.
Original PR description
If sale_timesheet is installed, the timer is activated by default. Task-2125111 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When a user creates another company, Odoo now refreshes the page automatically so multi-company options become available right away. This removes the need for users to manually reload the page to see the company selector.
Original PR description
Purpose ======= At the second res.company creation, the multicompany mode is 'enabled'. But to get the company selector dropdown, the user needs to reload the page. Specification ============= Force a reload at res.company creation, similarly to the forced reload when updating the language (lang) of the user. TaskID: 2127257 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update improves how Odoo web interface components share common event behavior, especially for keyboard navigation in fields. It also updates the underlying OWL framework and prepares a new foundation for future field components, helping developers deliver more consistent user interactions over time.
Original PR description
This commit's intention is to bring class inheritance of event handlers
to components.
Use case:
A component class may want to set generic event handlers for all classes
inheriting from it, in order to set shared event behavior from the start
It is the case in many parts of Odoo, in particular in the cases of fields
which need at least to react on some keyboard event for navigation
The way to implement such a behavior is to make use of the
`useRootNoteListeners` OWL hook, by passing an object of the form
`{eventName: handlerName}` in the constructor of the component's class
Description of the issue/feature this PR addresses:
Current behavior before PR:
Desired behavior after PR is merged:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prEmployee contract management is easier to use with clearer contract screens, better status visibility, and improved signature request flows. HR teams also receive automatic reminders before contracts expire, helping them act on renewals or follow-ups in time.
Original PR description
Pad:https://pad.odoo.com/p/r.69c133ed6fb15cce4c5d0772cc845d66 Task:https://www.odoo.com/web?debug=1#id=2049413&action=327&model=project.task&view_type=form&menu_id=4720
Forum question pages now show social sharing options only after the question has been validated. This prevents users from sharing links that would otherwise lead to missing or inaccessible pages.
Original PR description
Before this commit: when a user asks a question on a forum, share buttons are always showing even if question is validated or not and hence it will lead to 404 error. After this commit: when a user asks a question on a forum, share buttons will only show after a question is validated. Task: https://www.odoo.com/web#id=2064874&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.ce9674d408ec6564c8357037097e37df -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The recruitment website job list and job detail pages have been redesigned to provide a clearer, more engaging candidate experience. Businesses can now add a right sidebar to job listings and use existing website building blocks to better customize job descriptions.
Original PR description
Review and redesign website jobs pages task-2145266 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes an unused company-related field from the core base module. It helps keep the system cleaner and easier to maintain without changing expected business workflows.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Field Service tasks can now include products that require lot or serial number tracking, with a simple selection step from the task view. When a task is completed, the chosen lot or serial number is carried through to the related delivery operations, including multi-step routes, helping teams complete tracked product deliveries accurately.
Original PR description
Purpose ======= When a Field Service task is marked as done, the stock pickings linked to the SO are automatically confirmed. This flow works fine with a basic stock configuration, but it doesn't handle products tracked by Lots / Serial Numbers. Specifications =============== 1. Products tracked by lots or by serial number Display products tracked by lots or by serial number among the products selectable from a task. Manage SN from this kanban view, open a modal to select/remove a corresponding serial number. If a lot/sn is set through the modal, set the same value on the stock.picking when validating fsm task. 2. Avoid to remove already delivered products. 4. Multi-step routes: each picking should be validated when validation of FSM Task. TaskID: 2081191
Field Service users get smoother day-to-day workflows: service tasks can show customer addresses, offer map navigation, attach signed worksheet PDFs to the task history, and better align quotation and timesheet settings with company preferences. Sales-generated service tasks and demo data are also improved so teams have more accurate delivery details and setup defaults.
Original PR description
Purpose ====== Improve usability of the Field Service app and its related modules. Specifications =========== - If a task is generated from an SO, automatically set the delivery address as the…
Purpose ====== Improve usability of the Field Service app and its related modules. Specifications =========== - If a task is generated from an SO, automatically set the delivery address as the shiping address on the SO - Display the customer's address on fsm tasks like it used to. - If the 'Extra Quotations' feature is enabled from the settings, switch allow_quotations to true on all fsm projects and on new fsm projects. - Demo data: set the 'Device Installation & Maintenance' worksheet template on the 'Field Service' product - Add the worksheet report pdf to the note logged in the chatter when it is signed. - By default, allow_timesheet_timer should be set to true for SO projects generated from an SOL - In the 'My Tasks' menu: the hover should be 'Start Hour' (keep the 'Start Date' hover for fsm tasks in project and the 'Deadline' hover for project tasks) - Add a '-> Navigate to' link on tasks for which is_fsm is true. Clicking on it has the same effect as the 'Navigate to' button displayed on the map view. Task-2125111
HR contract screens are easier to use, with a clearer kanban view, improved contract forms, and better signature request layout. The update also helps HR teams track key contract dates by setting employee first contract dates, carrying over the last completed contract date, and creating automatic alerts before contracts expire.
Original PR description
Pad:https://pad.odoo.com/p/r.69c133ed6fb15cce4c5d0772cc845d66 Task:https://www.odoo.com/web?debug=1#id=2049413&action=327&model=project.task&view_type=form&menu_id=4720
Odoo can now handle assets that were already posted before the company started using the system, including assets from closed fiscal years. This helps businesses produce more complete depreciation reports and makes asset setup more reliable.
Original PR description
Task 2182787 When you start using Odoo, older data should be managed. Assets already booked for closed fiscal years should be well reported through the depreciation report. This task aims to easily Create them accordingly. While we are at it, we also use the changes done in the ORM recently with the editable compute. This makes the behavior more stable and the code more understandable.