-
Notifications
You must be signed in to change notification settings - Fork 42
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
[18.0][MIG] RMA #558
base: 18.0
Are you sure you want to change the base?
[18.0][MIG] RMA #558
Conversation
@JasminSForgeFlow Is this #572 included here? |
Yes, it was changed already |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An alignment of versions has been done in v17 #577. Could you take of aligning 17 and 18 again here?
Apart from that PR, there is potentially some others that were merged in 17 after this migration was created:
Please, make sure to leave anything behind.
* fix assignment of moves. * default qty in rma lines. * remove account dependency. * test and flake8 fixes.
… supplier [IMP]Separate menus for customer and supplier operations * Add active field to rma operation * Added tests * Fix travis * Fix create supplier rma from customer rma
* rma: receipt_policy selections not matching. * rma_sale: fix _prepare_rma_line_from_sale_order_line.
* remove unneded copy attributes. * simplify action_view methods. * fix wrong naming. * fix misplaced views. * fix wrong count and view actions for rma.orders in invoices. * fix error when installing the module. * remove unneded data update when preparing rma lines from invoice lines. * minor extra fixes.
* remove unneded copy and ondelete attributes. * simplify action_view methods. * fix rma line supplier view. * fix wizard. * extend README. * minor extra fixes.
… rma.order is optional.
qty_done -> quantity reserved_qty field does no exist anymore
When returning or delivering a serial product from a RMA, we will calculate by default its package. Later, it can be modyfied by the user.
… 'Customers' location
When looking at stock moves created from a rma group, it may be confusing knowing who's move is for which RMA line. This improvement should avoid these confusions.
… children of partner selected
When canceling a rma order line, it will also cancel the previous (orig) steps. Following steps (dest) can be managed with the propagate cancel option of the stock rules. This commit also avoid canceling a whole picking which is problematic in case of the use of RMA groups
The two modules have the same features, but the stock_restrict_lot is more used in other modules so changing the module used to match the OCA behavior.
…n/expedition Now the moves are filtered and only 1 move of the chain is selected to compute the quantity (the first one for reception and last one for expedition), so we should no longer ignore those to compute the quantities
e1179b8
to
6b7bb4e
Compare
6b7bb4e
to
7efd51f
Compare
Hi @JasminSForgeFlow could you also add #563, #550 and #555? |
One more #590 😅 |
Depends on: