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
When a sale line has a phantom product (mrp kits) the RMA would not be
possible as the wizard couldn't pair the components moves with the
product in the line. With this approach, we can at least return the
spare components of the original kit line.
We also need some hooks to intervine in the main methods, like in
invoicing.
[FIX+IMP] rma: usability
* IMP - Now the description will be an html son we can show rich styles
in the customers report.
* FIX - On locked sale orders it was need to unlock them to be able to open an RMA.
* IMP - Make the description label visible in the backend form so the
user can easily spot it.
* IMP - Added date and deadline filters.
* IMP - Added pending RMAs filter.
* IMP - Added late RMAs filter.
* IMP - Added danger decoration in tree view
rma 12.0.1.5.0
[UPD] Update rma.pot
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/
Translated using Weblate (Spanish)
Currently translated at 100.0% (268 of 268 strings)
Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/es/
[FIX] rma: return permissions
When a user with no stock manager permissions was doing the return, an
access error would raise.
rma 12.0.1.5.1
[FIX] rma: multicompany returns
The move was created with the default company
[UPD] Update rma.pot
rma 12.0.1.5.2
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/
[FIX] rma: non rma users confirm
The sudo had to be before calling the records
rma 12.0.1.5.3
[FIX] rma: pass company as record to procurement
This upstream commit expects `company_id` as a record instead of as an
integer id: 836ff55dc9
rma 12.0.1.5.4
[FIX] rma: internal users portal
Internal users with no RMA permissions got an access error when entering
the portal
[UPD] Update rma.pot
rma 12.0.1.6.0
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma/
