Wms sync#6
Closed
QuatschSalat wants to merge 430 commits into16.0from
Closed
Conversation
Currently translated at 100.0% (1 of 1 strings) Translation: wms-16.0/wms-16.0-stock_release_channel_warehouse_calendar Translate-URL: https://translation.odoo-community.org/projects/wms-16-0/wms-16-0-stock_release_channel_warehouse_calendar/it/
If there are several rules for a storage type (e.g.: in Pallets, you have Pallets/Pallets UK), don't bypass the next rules after the first condition evaluation.
…te script In order to skip unnecessary updates
…nsfers after unrelease return OCA#1053
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: wms-16.0/wms-16.0-shopfloor Translate-URL: https://translation.odoo-community.org/projects/wms-16-0/wms-16-0-shopfloor/
Allow no max nbr lines Allow no max volume Add test
As specific exceptions inherit from UserError, there is no need to do such change.
…y of picking type
When splitting is enabled, an over limit picking can be elected as first picking. In that case, the last device should be used. An over limit picking must be excluded only when splitting is disabled. When a trying to split a picking with a single move, there will be no split order as there is only one move. In this case, the picking must be used.
Tests broke because of this commit in a dependent module: OCA/delivery-carrier@9c8bd5c See this PR: OCA/delivery-carrier#1142 An outgoing picking is now considered its own "ship_picking_id" (which was not the case before) leading to more data than previously expected in the tests.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: wms-16.0/wms-16.0-stock_picking_batch_creation Translate-URL: https://translation.odoo-community.org/projects/wms-16-0/wms-16-0-stock_picking_batch_creation/
The "Need Release" counter on the Picking Type Kanban view was inconsistent with standard Odoo counters. Additionally, the layout broke when the count reached 1,000 or more, causing the number to overflow the card boundaries.
The `_get_today_start_end_datetime` function returned naive datetimes without accounting for the user's local timezone. Since Odoo stores datetimes in UTC, this caused incorrect filtering on the "Pickings to Process Today" screen for users in non-UTC timezones. Now, the function correctly calculates the start and end of the local day and converts those boundaries to UTC .
Currently translated at 100.0% (76 of 76 strings) Translation: wms-16.0/wms-16.0-stock_picking_batch_creation Translate-URL: https://translation.odoo-community.org/projects/wms-16-0/wms-16-0-stock_picking_batch_creation/it/
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi zusammen,
ich habe für Shopfloor mal einen Zwischenstand als PR in GitHub aufgemacht. Die meisten Änderungen darin sind keine Braking Changes. Ab da kommen weitere Commits mit Änderungen, die für uns größeren Einfluss haben. Da bin ich aktuell dran.
Hier eine Zusammenfassung der relevanten Module innerhalb von WMS:
stock_storage_type
--> Sollte uns aber nicht betreffen, da nicht genutzt. Habe ich gestern im Business Chat gefragt.
shopfloor_mobile
shopfloor_base
shopfloor