Daily updates from Odoo
Navigate
Branch
Wednesday, December 19, 2018
15 changes
New functionality added to Odoo
Scheduled tasks can now remember when they last ran and pass that timing information to their jobs. This helps processes that work over time ranges avoid extra shared settings updates, improving efficiency and reducing unnecessary cache refreshes.
Original PR description
Many crons process a dedicated queue of some sort (and either delete or disable the items once processed) but some may not want or be able to do that. In that case maintaining some sort of time range is convenient, and the cron itself doing so avoids weird solutions (like global settings). Task 1912648
Enhancements to existing features
Fleet vehicle reminders are now scheduled 30 days before the relevant date instead of 15 days. This gives teams more lead time to plan renewals, maintenance, or other vehicle-related actions and reduces the risk of last-minute follow-up.
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
This update removes a payroll accounting field that was not being used. It simplifies the module slightly and reduces clutter without changing day-to-day payroll accounting behavior.
Original PR description
This field seems to be never used. 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
When a kit is ordered, Odoo now applies the delivery, purchasing, or manufacturing routes of each individual component instead of using routes set on the kit product itself. This makes stock planning more accurate and alerts users when a kit is marked for manufacturing but lacks the required manufacturing bill of materials.
Original PR description
**Before this PR:** - The routes applied when a kit was ordered was the ones set on the kit. **After this PR:** - The routes of each components of the kits are applied independently and the routes set on the kit itself are ignored - A 'next activity' is logged when a kit as the route 'Manufacture' set and no BoM of type manufacture are linked to the kit TaskID : 1863856
This change makes default values in Point of Sale configurations easier to customize when importing setup data. It helps businesses load configuration records under the appropriate user context instead of being limited to the system administrator behavior.
Original PR description
## Description of the issue/feature this PR addresses: In case of import of data in pos.config you may want your data being inserted with another user than superadmin. This fix allows to manage the behavior by make it possible to override these methods ## Current behavior before PR: default field methods are NOT overridable in pos.config ## Desired behavior after PR is merged: default field methods ARE overridable in pos.config useful in inserted data -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Bill of Materials structure and cost reports are prepared to show clearer BoM information and support additional PLM details such as versions and ongoing engineering changes. This helps manufacturing teams review product structures and related changes more easily when PLM is in use.
Original PR description
Description of the issue/feature this PR addresses:
- Task : https://www.odoo.com/web#id=1875677&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
- Pad : https://pad.odoo.com/p/r.2ca892cd59cf85ad42ca442b7240b33e
Current behavior before PR:
- Improve the BoM Cost and Structure Report
Desired behavior after PR is merged:
- For Enterprise Only (as related to PLM app) :
- Add a column for the BoM version https://drive.google.com/a/odoo.com/file/d/1Bckk0-oT_RRHWf-OOZhCmHefhYayr6Ii/view?usp=drivesdk
(only visible if PLM is installed + visible on BoM Structure and BoM Cost reports)
- Add a column for the ongoing ECOs on the product https://drive.google.com/a/odoo.com/file/d/106dIj5Cm6uLZdj_f0wAhuTD0BPMpcFx8/view?usp=drivesdk
(only visible if PLM is installed + only visible on BoM Structure, not BoM cost report)
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prUsers in debug mode can now update the OdooBot state field shown in their preferences. This resolves a mismatch where the setting was visible but could not be changed, improving administrative consistency.
Original PR description
Before this commit it was imposible to write on odoobot_state even though it is showed in user preferences (debug mode) -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Event organizers can now generate standard calendar invitation files directly from the Events app, without needing the Website Events app. This replaces reliance on an outdated Outlook-specific integration and improves compatibility with common calendar tools.
Original PR description
Ics file generation should be possible even when only event is installed as it is a basic feature of events. Moreover we need to be able to generate such files in order to replace the old outlook api used in the event templates, api which is not supported anymore. We decided to use ics files because it is supported by most calendar schedulers hence working with outlook. Linked to task #1853063 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Manufacturing users can now see the bill of materials version and whether engineering changes are in progress for a product. This helps teams spot possible upcoming cost or design changes before making decisions based on the current BoM.
Original PR description
- Task : https://www.odoo.com/web#id=1875677&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 - Pad : https://pad.odoo.com/p/r.2ca892cd59cf85ad42ca442b7240b33e
The Documents app now opens to a global view that shows documents from all accessible folders instead of selecting a folder by default. Users can return to this all-documents view from the folder selector, making it easier to find and manage files across the organization.
Original PR description
After this commit, the default kanban attachment view is the document's kanban view. it is now also possible to select a "all" menu, in the folder selection to display a global view (showing all documents available across all folders) Task: #1905664
Resolved issues and error corrections
This fixes a display issue where dragging kanban cards with cover images created extra blank space, making it harder to place cards accurately. Users can now reorder image-based kanban records more reliably without accidentally opening the record after dragging.
Original PR description
While dragging kanban record which have a cover image set, the kanban view creates extra space, which makes it difficult to properly target a position. This is because of a jquery.ui issue for…
While dragging kanban record which have a cover image set, the kanban view creates extra space, which makes it difficult to properly target a position. This is because of a jquery.ui issue for sortable when helper=clone is used. In that case, then jquery.ui sortable will create a clone of current element after hiding it. Note that jquery.ui tries to get height to current dragged element after making it hidden(display: none) and display: none, so the element does not return actual height and hence it gives innerHeight which considers height of the image also and extra space is generated. An alternative solution is to add start event in sortable option and 1) show ui.item 2) get height of the element and 3) hide ui.item, which gives proper height of the current dragged element But removing helper=clone will also fix the issue and is not actually required. Note that some special care had to be done to prevent the click from the drag and drop operation to actually open the record. Related to task: #1865788 Closes: #25734 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 corrects how cells are highlighted when users move the mouse over pivot tables. It makes data exploration clearer and avoids confusing visual feedback in reporting views.
Original PR description
Task: https://www.odoo.com/web#id=1916889&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.fd5456734abb79ff758d4ef413645749 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes an issue in Sign where editing a PDF template could trigger a browser error because a script was loaded more than once. Users should have a smoother experience when opening and editing PDF templates, with the needed styling still applied correctly.
Original PR description
Task: https://www.odoo.com/web?#id=1889748&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.1ecfa1ac872613749b4ca8797cb61c11
Code cleanup and technical improvements
This update reorganizes internal JavaScript customizations in Email Marketing to make the views easier to maintain and less fragile. It also keeps drag-and-drop available in more kanban situations, only disabling it for specific groupings where it should not be used.
Original PR description
Task #1909424 The mass_mailing module used a lot of JS "include" to override the behavior of the kanban view and the html_frame widget. This commit cleans the overrides by using proper inheritance with "extend" instead of "include". It also slightly changes the current behavior of the mass_mailing kanban view to disable the drag and drop feature only when the view is grouped by "state" or "email_from". (Before this commit, the drag and drop feature was disabled for ALL fields). -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update cleans up internal code used by mass mailing screens, making the email campaign views easier to maintain. It also makes campaign board drag-and-drop more flexible by only disabling it for specific groupings where moving items could be inappropriate.
Original PR description
Task #1909424 Community commit: afa71a4ec8d8383e15a8579d49ac31a8483eadbb The mass_mailing module used a lot of JS "include" to override the behavior of the kanban view and the html_frame widget. This commit cleans the overrides by using proper inheritance with "extend" instead of "include". It also slightly changes the current behavior of the mass_mailing kanban view to disable the drag and drop feature only when the view is grouped by "state" or "email_from". (Before this commit, the drag and drop feature was disabled for ALL fields).