[18.0][MIG] delivery_purchase: Migration to 18.0 #966
Conversation
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
36 tasks
BhaveshHeliconia
force-pushed
the
18.0-mig-delivery_purchase
branch
from
64a4b21 to
b87b0a3
Compare
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
github-actions
bot
added
the
stale
Co-authored-by: Pedro M. Baeza <[email protected]> Co-authored-by: cubells <[email protected]> [UPD] Update delivery_purchase.pot
Auto-create (delivery) order lines when picking are marked as done TT45656
…rchase order header In v13 it already appeared in the header, and in v14 by mistake it had been moved to the "Other information" tab because that was where the company_id field was currently located. The carrier price is now hidden if there is no carrier set (to avoid confusion). TT45656
If we have a delivery price of 10 on the order, it is expected to show 10 on the picking (without needing to be set to that amount when set the picking as done). TT45656
…n tests of other modules TT45656
TT46563 Co-authored-by: carolinafernandez-tecnativa
…cking_orig_id) field to purchase order lines If there are several pickings for an order and several have carriers, several purchase order lines (is_delivery) will be created but we need to know the origin (picking) that created them. TT50146
Currently translated at 100.0% (14 of 14 strings) Translation: delivery-carrier-16.0/delivery-carrier-16.0-delivery_purchase Translate-URL: https://translation.odoo-community.org/projects/delivery-carrier-16-0/delivery-carrier-16-0-delivery_purchase/it/
BhaveshHeliconia
force-pushed
the
18.0-mig-delivery_purchase
branch
from
b87b0a3 to
ae91005
Compare
github-actions
bot
removed
the
stale
Use case example: - Create a sales order and use the Dropshipping route - Set the delivery address as France, for example - Create a rule-based carrier only available for France - Confirm the sales order - Confirm the purchase order - Set the previously created carrier on the delivery note - The carrier must be applied correctly, using the delivery address (France) as a reference TT58174
Use case example: - Create a sales order and use the Dropshipping route - Set the delivery address as France, for example - Create a rule-based carrier only available for France - Confirm the sales order - Set the previously created carrier on the purchase order - The carrier must be applied correctly, using the delivery address (France) as a reference TT58174
BhaveshHeliconia
force-pushed
the
18.0-mig-delivery_purchase
branch
from
ae91005 to
9aa6d74
Compare
|
@victoralmau : Done — please review when you get a chance. Thanks! |
|
Please, cherry-pick #1061 to commit history before migration commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
No description provided.