* Standard procedure.
* Transfer view groups to nodes.
* Adjusted upstream changed field names.
* Converted onchanges to computed writable fields.
* Replace `Form` by direct dictionary vals in record creation, as they
don't handle now properly multiple existing fields in the view, and
computed writable improve the compatibility on new values.
* Replace domain returned on onchange by static domain in field.
* Change maintainer.
TT44213
[UPD] Update rma.pot
[UPD] README.rst
[UPD] README.rst
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-16.0/rma-16.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-16-0/rma-16-0-rma/
If we place an RMA from the stock picking return wizard, we want to
avoid setting the new moves to refund as that will affect the related
sale lines delivered quantities count.
TT42021
When we delete the reception for an RMA, we're setting it to draft
automatically so we can confirm it again and create a new reception.
This is unconvenient when the RMA is cancelled, as we don't wan't to
reopen it automatically.
TT41943
Up to v12, account.invoice, was allowed for a wide variety of users. In
this version though, with account.move conversion, those permissions are
quite restricted.
We want to keep the possibility to open a refund for the RMA users.
Although only Invoicing users will be able to post it anyway.
TT34644
In the tree view, the RMA code (`name` field) tends to lose in the
column width share. The result is will be the trimming of the reference
with ellipsis (...).
As this is very relevant information, we want to ensure a minimum width
for such reference.
TT35107
Sometimes there's no choice to return, refund or replace an RMA for
different reasons. For example, when the customer doesn't want to repair
the product because that would be too expensive. We still want finish
the RMA and document the reasons. This improvement allows it.
TT34164
Since odoo/odoo#75823, the wizard lines have the field uom_id related to
move.product_uom and readonly=False, so if you call directly to
wiz.onchage_picking_id a write in stock move is executed and the warning raises,
although we don't really do any UoM change.
We avoid it using the `Form` to perform the wizard update.
Having a default responsible value as it was defined doesn't behave
right when the user it's a portal one or the petition comes from a
sudo().
Also, by design it was expected to have a default team if it wasn't
defined, but as it was implemented that wasn't possible.
TT32056
Now we can configure if an automatic notification should be sent when we
receive the goods from an RMA in our warehouse
If we've got `rma_sale` or `website_rma` we can also configure draft
notifications so when the customer places an RMA from the portal the
receive an acknowledge email.
TT29595
