-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
[16.0][ADD] add rma_reason & sale_rma_reason #409
base: 16.0
Are you sure you want to change the base?
Conversation
429d797
to
0ddd67f
Compare
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.
b361a86
to
324b5a8
Compare
3223b9c
to
18c0169
Compare
Specifying the RMA reason when creating an RMA order is crucial for effective inventory management, quality control, and customer service. It helps categorize returned items accurately, identify recurring product issues, and improve overall product quality. This data enables customer service to address issues more effectively and enhances the customer experience. This addon allows RMA managers to pre-configure possible reasons users can specify when creating the RMA order.
b32941b
to
7886fb6
Compare
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.
LGTM
"name": "Rma Reason", | ||
"version": "16.0.1.0.0", | ||
"license": "AGPL-3", | ||
"author": "Raumschmiede GmbH,BCIM,ACSONE SA/NV,Odoo Community Association (OCA)", |
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.
I think Raumschmiede GmbH
should go in the CREDITS file, not as author, being the paying customer, isn't it?
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.
@jbaudoux , fine with you?
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.
They are the original author of the module, not the paying customer of this OCA port
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.
But you should not add them at the top of the file that were not there originally.
<th class="text-start">Requested operation</th> | ||
<th | ||
class="text-start" | ||
name="operation" |
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.
And you can take the occasion to name all the elements.
name="operation" | |
name="th_operation" |
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.
is it really needed? As in the xpath, we must already specify the node
<xpath expr="//th[@name='operation']" position="before">
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.
Adding the same name several times is not a good practice IMO. It's true that selectors are done usually with the HTML tag, but to get an absolute element, better with unique names.
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.
You are right @pedrobaeza in the case of the id
element attribute since this one is expected to be unique across the full dom. But for the name
, it seems to me to be redundant.
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.
OK, it's not critical.
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.
Just as reference, Odoo follows my same suggestion:
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.
I would say it should be at developer's discretion as both approaches provide a unique way of xpath anchor.
@@ -147,7 +150,7 @@ | |||
t-att-value="data['picking'] and data['picking'].id" | |||
/> | |||
</td> | |||
<td class="text-start"> | |||
<td class="text-start" name="operation"> |
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.
<td class="text-start" name="operation"> | |
<td class="text-start" name="td_operation"> |
This PR has the |
94908ba
to
b0f2031
Compare
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.
LG, not tested yet
@sbejaoui I would prefer to have the reason before the operation on the wizard as, in my opinion, it makes more sense to first choose a reason and then an operation. Some operations may not be valid for some reason |
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.
Can you add the reason also in the stock picking return ? Like you did on SO wizard.
You can also create RMAs from there
1696b0a
to
a8ef693
Compare
a8ef693
to
694fb4d
Compare
[IMP] rma_reason: add rma reason to stock return wizard
694fb4d
to
9a3a65b
Compare
@jbaudoux , can you plz update your review |
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.
Tested, looks good
Specifying the RMA reason when creating an RMA order is crucial for effective inventory management, quality control, and customer service. It helps categorize returned items accurately, identify recurring product issues, and improve overall product quality. This data enables customer service to address issues more effectively and enhances the customer experience.
This addon allows RMA managers to pre-configure possible reasons users can specify when creating the RMA order.
fixes #405
needs: #410
cc/ @jbaudoux , @lmignon , @rousseldenis