[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_sale 12.0.1.5.0
Translated using Weblate (Spanish)
Currently translated at 100.0% (62 of 62 strings)
Translation: rma-12.0/rma-12.0-rma_sale
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma_sale/es/
- Proper dependency is `sale_stock`, not `sale`, as we are using some fields added
by this module.
- Propagate salesman from sales order when available.
TT25525
rma_sale 12.0.1.4.1
- Now it's possible to open several RMAs in a sale order from the portal
- A new comment button has been added to allow the portal user to enter
relevant information like serial numbers o issue description.
- If the requested operation isn't set no RMA will be opened
- The RMA product qty is now a numeric control with limits according to
the qty available to return
[FIX] rma,rma_sale: fix linter errors
[UPD] Update rma_sale.pot
rma_sale 12.0.1.4.0
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma_sale
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma_sale/
- Fix thrown error when trying to download a picking from the portal.
- Add the hook method to prepare RMA values from the return pick wizard.
- Add the access rule for portal users.
- Show the portal 'Request RMAs' button on the sales page only to users
related to the sales order.
[UPD] Update rma_sale.pot
rma_sale 12.0.1.3.0
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma_sale
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma_sale/
[FIX] rma: views permissions
Regular users don't have permissions to rma models, so we should avoid
loading views that lead to permission errors.
TT24986
rma_sale 12.0.1.1.0
[FIX] rma_sale: portal permissions
Some operations need to be sudoed to be reachable by the portal user
[UPD] Update rma_sale.pot
rma_sale 12.0.1.1.1
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma_sale
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma_sale/
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma_sale
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma_sale/
[IMP] rma: teams flow
- If no RMA Team is set, we'll assign a default one to the new RMA.
- A sequence is now used to search for the top team and assign it.
- No default user is assigned when it's not in the context (i.e. portal
rmas).
[UPD] Update rma_sale.pot
rma_sale 12.0.1.2.0
Update translation files
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.
Translation: rma-12.0/rma-12.0-rma_sale
Translate-URL: https://translation.odoo-community.org/projects/rma-12-0/rma-12-0-rma_sale/
* 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
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
