[FW][FIX] sale_purchase: read service_to_purchase from the order's company #194947
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
|
|
robodoo
added
forwardport
|
@ivantodorovich @ticodoo cherrypicking of pull request #177659 failed. stdout: Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?). In the former case, you may want to edit this PR message as well. More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
Previous fix: eacb2a7 fixed the following bug: Steps to reproduce: 1. Create two companies: Company A and Company B 2. Create a service product 3. Configure the product to be purchased on Company A and not on Company B 4. Create a sales order on Company B, while logged in Company A 5. Confirm the order Expected result: The service PO is created on Company B, even though it was configured not to. --- But this fix did not update the other associated spots that suffer from the same issue, specifically: - When to display the applicable decreased qty - PO adjustment warning - When POs are associated with increased/decreased SO values So this commit fixes them now. X-original-commit: 9b85412
ticodoo
force-pushed
the
18.0-16.0-fix-service-to-purchase-multi-company-xC5v-fw
branch
from
b2a07fc to
5819623
Compare
|
@robodoo r+ |
adhoc-cicd-bot
pushed a commit
to adhoc-cicd/odoo-odoo
that referenced
this pull request
Jan 26, 2025
Previous fix: eacb2a7 fixed the following bug: Steps to reproduce: 1. Create two companies: Company A and Company B 2. Create a service product 3. Configure the product to be purchased on Company A and not on Company B 4. Create a sales order on Company B, while logged in Company A 5. Confirm the order Expected result: The service PO is created on Company B, even though it was configured not to. --- But this fix did not update the other associated spots that suffer from the same issue, specifically: - When to display the applicable decreased qty - PO adjustment warning - When POs are associated with increased/decreased SO values So this commit fixes them now. closes odoo#194947 X-original-commit: 9b85412 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
gamarino
pushed a commit
to numaes/numa-public-odoo
that referenced
this pull request
Jan 27, 2025
Previous fix: eacb2a7 fixed the following bug: Steps to reproduce: 1. Create two companies: Company A and Company B 2. Create a service product 3. Configure the product to be purchased on Company A and not on Company B 4. Create a sales order on Company B, while logged in Company A 5. Confirm the order Expected result: The service PO is created on Company B, even though it was configured not to. --- But this fix did not update the other associated spots that suffer from the same issue, specifically: - When to display the applicable decreased qty - PO adjustment warning - When POs are associated with increased/decreased SO values So this commit fixes them now. closes odoo/odoo#194947 X-original-commit: 9b854120ad68ab011bd9bfafb47ac4ad4cb5ca87 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
adhoc-cicd-bot
pushed a commit
to adhoc-cicd/odoo-odoo
that referenced
this pull request
Jan 29, 2025
Previous fix: eacb2a7 fixed the following bug: Steps to reproduce: 1. Create two companies: Company A and Company B 2. Create a service product 3. Configure the product to be purchased on Company A and not on Company B 4. Create a sales order on Company B, while logged in Company A 5. Confirm the order Expected result: The service PO is created on Company B, even though it was configured not to. --- But this fix did not update the other associated spots that suffer from the same issue, specifically: - When to display the applicable decreased qty - PO adjustment warning - When POs are associated with increased/decreased SO values So this commit fixes them now. closes odoo#194947 X-original-commit: 9b85412 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
adhoc-cicd-bot
pushed a commit
to adhoc-cicd/odoo-odoo
that referenced
this pull request
Jan 29, 2025
Previous fix: eacb2a7 fixed the following bug: Steps to reproduce: 1. Create two companies: Company A and Company B 2. Create a service product 3. Configure the product to be purchased on Company A and not on Company B 4. Create a sales order on Company B, while logged in Company A 5. Confirm the order Expected result: The service PO is created on Company B, even though it was configured not to. --- But this fix did not update the other associated spots that suffer from the same issue, specifically: - When to display the applicable decreased qty - PO adjustment warning - When POs are associated with increased/decreased SO values So this commit fixes them now. closes odoo#194947 X-original-commit: 9b85412 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
StephaneMangin
pushed a commit
to camptocamp/odoo
that referenced
this pull request
Feb 6, 2025
Previous fix: eacb2a7 fixed the following bug: Steps to reproduce: 1. Create two companies: Company A and Company B 2. Create a service product 3. Configure the product to be purchased on Company A and not on Company B 4. Create a sales order on Company B, while logged in Company A 5. Confirm the order Expected result: The service PO is created on Company B, even though it was configured not to. --- But this fix did not update the other associated spots that suffer from the same issue, specifically: - When to display the applicable decreased qty - PO adjustment warning - When POs are associated with increased/decreased SO values So this commit fixes them now. closes odoo#194947 X-original-commit: 9b85412 Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
fw-bot
deleted the
18.0-16.0-fix-service-to-purchase-multi-company-xC5v-fw
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Steps to reproduce:
Expected result:
The service PO is created on Company B, even though it was configured not to.
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: #194432
Forward-Port-Of: #177659