-
-
Notifications
You must be signed in to change notification settings - Fork 205
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
RMA reason #405
Comments
Well, that's what the RMA operations are for. The module pre-creates three of them, but you can change them or add as many as you want to. And customers in the sale portal can select them and even add notes per return line |
In fact, it serves two different purpose. |
I understand. There's a similar optional feature (group_rma_manual_finalization) for manual finalization reasons. Maybe you could propose a similar approach. |
Can you provide the link to that module, I can't find it ? |
It's in the rma/rma/models/res_config_settings.py Lines 9 to 13 in eeb0672
|
I updated the issue with the proposed solution specifications |
Add rma reason
To improve quality, it is good to understand why an RMA has been created.
For this I'd like to have a required RMA reason defined on the RMA. This would be also available and required on the SO wizard on each line (or globally)
Make a
rma_reason
module that depends onrma
rma.reason
with name, action, company + unique(name, company). Security: read for rma user, crud for rma manager_ensure_required_fields
Requested operation
Make a
rma_sale_reason
module that depends onrma_sale
andrma_reason
The text was updated successfully, but these errors were encountered: