Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FIX] stock: multiple orderpoint #40573

Closed
wants to merge 1 commit into from

Conversation

@sle-odoo
Copy link
Contributor

sle-odoo commented Nov 20, 2019

  • the oderpoint_id field on the purchase order line wasn't used to not
    merge the po lines
  • if the orderpoint_id field is set, use the orderpoint location

task-2001462

@sle-odoo

This comment has been minimized.

Copy link
Contributor Author

sle-odoo commented Nov 20, 2019

@C3POdoo C3POdoo added the RD label Nov 20, 2019
@sle-odoo sle-odoo force-pushed the odoo-dev:master-orderpoint-sle branch from 68d4e2c to 3976a79 Dec 2, 2019
@robodoo robodoo added CI 🤖 and removed CI 🤖 labels Dec 2, 2019
@sle-odoo sle-odoo force-pushed the odoo-dev:master-orderpoint-sle branch from 3976a79 to 0e1c8a6 Dec 2, 2019
@robodoo robodoo removed the CI 🤖 label Dec 2, 2019
- the oderpoint_id field on the purchase order line wasn't used to not
  merge the po lines
- if the orderpoint_id field is set, use the orderpoint location to
  create the move
- if multiple stock moves with different source locations go through
  `_merge_moves`, they should obviously NOT be merged
- `virtual_available` computed field was not being invalidated when the
  context keys "warehouse" and "location" changed

task-2001462
@sle-odoo sle-odoo force-pushed the odoo-dev:master-orderpoint-sle branch from 0e1c8a6 to f086433 Dec 2, 2019
@amoyaux

This comment has been minimized.

Copy link
Contributor

amoyaux commented Dec 2, 2019

robodoo r+

robodoo pushed a commit that referenced this pull request Dec 2, 2019
- the oderpoint_id field on the purchase order line wasn't used to not
  merge the po lines
- if the orderpoint_id field is set, use the orderpoint location to
  create the move
- if multiple stock moves with different source locations go through
  `_merge_moves`, they should obviously NOT be merged
- `virtual_available` computed field was not being invalidated when the
  context keys "warehouse" and "location" changed

task-2001462

closes #40573

Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>
@robodoo robodoo closed this Dec 2, 2019
@robodoo robodoo deployed to merge Dec 2, 2019 Active
bbh-odoo added a commit to odoo-dev/odoo that referenced this pull request Dec 9, 2019
- the oderpoint_id field on the purchase order line wasn't used to not
  merge the po lines
- if the orderpoint_id field is set, use the orderpoint location to
  create the move
- if multiple stock moves with different source locations go through
  `_merge_moves`, they should obviously NOT be merged
- `virtual_available` computed field was not being invalidated when the
  context keys "warehouse" and "location" changed

task-2001462

closes odoo#40573

Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>
aab-odoo added a commit to odoo-dev/odoo that referenced this pull request Dec 12, 2019
- the oderpoint_id field on the purchase order line wasn't used to not
  merge the po lines
- if the orderpoint_id field is set, use the orderpoint location to
  create the move
- if multiple stock moves with different source locations go through
  `_merge_moves`, they should obviously NOT be merged
- `virtual_available` computed field was not being invalidated when the
  context keys "warehouse" and "location" changed

task-2001462

closes odoo#40573

Signed-off-by: Arnold Moyaux <amoyaux@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants
You can’t perform that action at this time.